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

  • Ok, here's the quick fix - Translation Aggregator 0.4.6 (WWWJDIC, injection dialog thing fixed, process list autoupdated - getting ready to add the last is what broke the injection dialog).

    tamers182 (If that is your real name):

    Just think of fonts as your little friends, rather than as the conniving bastards they really are, and the issue should clear right up.

    Curiously, it's working fine for me, except for bitmap fonts (The pixelated ugly ones), and those don't work in the MeCab and JParser Windows, either.

    You are on XP SP1 or later, right? Can't really see how that'd make everything but the font face work, but you never know.
    Last edited by ScumSuckingPig; 05-03-2011, 06:16 PM.

    Comment


    • Originally posted by ScumSuckingPig View Post
      Ok, here's the quick fix - Translation Aggregator 0.4.6 (WWWJDIC, injection dialog thing fixed, process list autoupdated - getting ready to add the last is what broke the injection dialog).

      tamers182 (If that is your real name):
      It isn't.

      Originally posted by ScumSuckingPig View Post
      Just think of fonts as your little friends, rather than as the conniving bastards they really are, and the issue should clear right up.

      Curiously, it's working fine for me, except for bitmap fonts (The pixelated ugly ones), and those don't work in the MeCab and JParser Windows, either.

      You are on XP SP1 or later, right? Can't really see how that'd make everything but the font face work, but you never know.
      I do think of fonts as friends, as long as they do what they are supposed to. Not as good friends, but as some sort of bad friends from high-school time.

      I'm using windows 7 x86.

      Here is the screen i've posted a few pages back:

      I've got a similar problem to the one i've had about half a year ago:

      Back than TA couldn't use different font settings. I could change from the standart font to Comic Sans for example, but if i restarted TA after changing it, the font looked odd, with a wierd letterspacing. Also it wouldn't respond to any changes to the font i've made after that. The only way to fix this was to make TA's .ini read only with the standart font, and change the font manually each time.

      Since i'm using only MeCab and jParser for the kanji/words i don't know for quite a while now, i haven't noticed the following bug:

      On a Japanese Windows 7 (x86), the same font problem occurs as described above. This bug only occurs to all the TA windows EXEPT MeCab and jParser, wich is why i haven't noticed that until now...

      Also this bug only occurs as long as the formats of Windows (language setting) are set to Japanese (first tab of the region and language settings).

      Once i set this formats/language option to something western (german in my case), it works as it did last year on my german Win 7 -- until i save the font settings (close TA with changed fonts).

      The Screenshot i've attached shows this bug (deleted TA's .ini, it would work with western formats now) and the windows language setting it's related to. Notice how MeCab and jParser work fine please.


      I hope you can give me a hint, SSP, i couldn't find any workaround like last time...

      Changing the language settings isn't an option, i've read (and expirienced) that several VN's (Ohime-sama wa leo, Hara Miko for example) either won't work with just the setting for non-unicode applications set to japanese, or will have force closes/bugs at some points (Hara Miko).

      Playing with this font on a tv also wouldn't be fun...

      Screenshot:
      Spoiler

      Comment


      • Try this.

        Note that it changes a field which, according to official MS spec "has no effect on the text displayed by a rich edit control".
        Attached Files

        Comment


        • Originally posted by ScumSuckingPig View Post
          Try this.

          Note that it changes a field which, according to official MS spec "has no effect on the text displayed by a rich edit control".
          No Joy...


          Very evil, indeed.

          Comment


          • Originally posted by tamers182 View Post
            No Joy...


            Very evil, indeed.
            Curious. Changing the LCID to Japanese message up my font (So MS's docs *are* wrong). Too bad changing it to US English didn't fix the issue.

            Comment


            • Do you have any idea what this could be?

              Why is it working for you?

              Comment


              • Originally posted by tamers182 View Post
                Do you have any idea what this could be?

                Why is it working for you?
                I blame it all on Microsoft. I really don't know what the issue is. It's some sort of non-API (extra-API?) feature (As in the docs for the APIs I'm using don't say a thing about this behavior). Unless MS clearly documents the behavior in some discoverable location, not much I can do but try things randomly, which is not exactly the most interesting activity.

                Comment


                • Tested font issue on XP with Japanese regional and language settings.
                  Spoiler
                  It seems like this feature is in effect:


                  System is assuming japanese writing by default, therefore font selection only works with real japanese fonts like MS Gothic etc. Restarting TA is also OK.
                  #1 MS Gothic font test:


                  If non-japanese font is selected, system takes random japanese font for japanese and english characters (looks like it treats english as subset of japanese) and selected font for others (assuming support).
                  #2 Impact font test:

                  Note how only cyrillic characters are displayed correctly because Impact does not support japanese.

                  #3 Also in this case, after TA is restarted, font in Rich boxes is always resets to Lucida Sans Unicode regardless of previous selection:

                  Previous font can be restored by entering font dialog and immediately pressing OK. Seems like a bug in TA initialization.

                  Tested also TA 0.3.2 and only difference was on #2. It chose another random japanese font, looking very differently than rough looking one on picture above (with latest version).
                  読んでみた。 読んでみようとした。 読めたらいいな、と思った。

                  Comment


                  • Originally posted by Setsumi View Post
                    Previous font can be restored by entering font dialog and immediately pressing OK. Seems like a bug in TA initialization.
                    I can't reproduce that. I start with a fresh TA 0.4.6 install, set font to impact, quit, restart, and the font is still being used everywhere. Using one with pre-existing config files, get the same behavior.

                    Edit: Do you get the same behavior in TA 0.4.5, too? There was one experimental font change to 0.4.6 which didn't seem to make a difference, but theoretically could with different text edit versions.

                    Edit: Can->can't.
                    Last edited by ScumSuckingPig; 05-04-2011, 05:37 AM.

                    Comment


                    • @ScumSuckingPig: Tested TA 0.4.5 with vmware for easy messing around.

                      Spoiler
                      Originally posted by ScumSuckingPig View Post
                      I can't reproduce that. I start with a fresh TA 0.4.6 install, set font to impact, quit, restart, and the font is still being used everywhere.
                      I have this behaviour too on non-japanese locale.
                      #1 Impact font test:

                      All is well.

                      Problem only occurs on japanese locale (non-unicode system language). Regional / location settings doesn't matter.

                      #2 Now, restart TA on japanese locale:

                      Note that font visible in the box is reset to something looking similar to Lucida Sans Unicode.

                      #3 Now, open font dialog:


                      #4 And press OK:

                      Now font is "restored" to that it actually looks like when you tinker with it via font dialog. Restarting TA resets visible font to #2 again, so you need to "restore" it every time. I observe this on any TA version.
                      読んでみた。 読んでみようとした。 読めたらいいな、と思った。

                      Comment


                      • Thanks for looking into that, Setsumi. I suppose the only real fix for that may be to force the locale to be non-Japanese.

                        Comment


                        • You told me to do that before (applocale set to US), and that didn't work for me.

                          Comment


                          • Originally posted by tamers182 View Post
                            You told me to do that before (applocale set to US), and that didn't work for me.
                            Indeed. So MS apparently isn't really using the locale you tell it to. The edit controls may be using system default instead of active or something.

                            Comment


                            • Tested fonts some more.

                              Spoiler
                              MS WordPad uses the same RICHEDIT50W as TA. It just switches font to MS Gothic if you type japanese and blocks any attempts to change such text to any (illegal) western font. Thus we have multi-font situation in TA too, and RICHEDIT50W is simple and stupid.
                              I set default font to Impact and pasted some text:

                              Note how it switched to MS Gothic after first japanese character and stayed that way. So its no good to set in TA some default font (and its not even working because english is lumped with japanese somehow) and hope for the best, because text can be mixed.

                              Tried Impact font test using selections instead of "ALL":
                              Code:
                              	CHARRANGE charr;
                              	charr.cpMin = 0;
                              	charr.cpMax = 65534;
                                  SendMessage(hWndEdit, EM_EXSETSEL, (WPARAM) 0, (LPARAM) &charr);
                                  SendMessage(hWndEdit, EM_SETCHARFORMAT, SCF_SELECTION, (LPARAM) &format);

                              It worked, but only in WWWJDIC (why???) This must be done after each text change too.

                              Looked into SetFont() function:
                              Code:
                              void TranslationWindow::SetFont() {
                                if (hWndEdit) {
                                  CHARFORMAT format; // not cleared
                                  format.bCharSet = // garbage
                                  format.bPitchAndFamily = // garbage
                                  format.cbSize = sizeof(format);
                                  format.dwMask = CFM_COLOR | CFM_BOLD | CFM_FACE | CFM_SIZE | CFM_BOLD | CFM_FACE | CFM_ITALIC | CFM_UNDERLINE | CFM_STRIKEOUT;
                              So that "font save" issue is actually other way around. If you select illegal western font, its not used at all, and visible font controlled by font family in format.bPitchAndFamily containing random junk. So you actually "corrupt" font when selecting something, and restarting TA "cures" font as it should be.
                              Last edited by Setsumi; 05-05-2011, 06:53 AM.
                              読んでみた。 読んでみようとした。 読めたらいいな、と思った。

                              Comment


                              • Originally posted by Setsumi View Post
                                Tested fonts some more.

                                Spoiler
                                MS WordPad uses the same RICHEDIT50W as TA. It just switches font to MS Gothic if you type japanese and blocks any attempts to change such text to any (illegal) western font. Thus we have multi-font situation in TA too, and RICHEDIT50W is simple and stupid.
                                I set default font to Impact and pasted some text:

                                Note how it switched to MS Gothic after first japanese character and stayed that way. So its no good to set in TA some default font (and its not even working because english is lumped with japanese somehow) and hope for the best, because text can be mixed.

                                Tried Impact font test using selections instead of "ALL":
                                Code:
                                	CHARRANGE charr;
                                	charr.cpMin = 0;
                                	charr.cpMax = 65534;
                                    SendMessage(hWndEdit, EM_EXSETSEL, (WPARAM) 0, (LPARAM) &charr);
                                    SendMessage(hWndEdit, EM_SETCHARFORMAT, SCF_SELECTION, (LPARAM) &format);

                                It worked, but only in WWWJDIC (why???) This must be done after each text change too.

                                Looked into SetFont() function:
                                Code:
                                void TranslationWindow::SetFont() {
                                  if (hWndEdit) {
                                    CHARFORMAT format; // not cleared
                                    format.bCharSet = // garbage
                                    format.bPitchAndFamily = // garbage
                                    format.cbSize = sizeof(format);
                                    format.dwMask = CFM_COLOR | CFM_BOLD | CFM_FACE | CFM_SIZE | CFM_BOLD | CFM_FACE | CFM_ITALIC | CFM_UNDERLINE | CFM_STRIKEOUT;
                                So that "font save" issue is actually other way around. If you select illegal western font, its not used at all, and visible font controlled by font family in format.bPitchAndFamily containing random junk. So you actually "corrupt" font when selecting something, and restarting TA "cures" font as it should be.
                                What does it mean that it worked at the second screenshot? did you find a fix for it?

                                Comment

                                Working...
                                X