Home Artists Posts Import Register

Content

Hello everyone,

This is a quick note about version 3.4.15

What has been changed

Translator++ ver. 3.4.15

  • Update : Better code escaping regexp for RPG Maker
  • Fix : Google Cloud unable to translate other than Japanese
  • Update : Google cloud translator engine to 1.4
  • Fix : Sometime when closing the option windows the configuration is not saved
  • Fix : Better performance for addon loader
  • Fix : Unable to resize column via context menu
  • Fix : RenParser can now export selected files
  • Fix : replaces fs with graceful-fs to avoid error when opening or writing a lot of files at once.
  • Fix : Renpy updated to ver 0.6, more stable file handling, parsing & writing progress now displayed on the progress window.
  • Fix : KAG Parser, added new alternative parser, supposed to be more accurate.
  • Fix : KAG Parser now able to export files partially
  • Update : KAGParser ver.0.6
  • Fix : Cleaning up SourceMaps that causes warnings on developer console
  • And more

More into KAGParser

I plan to create an addon for TyranoBuilder. Because the Tyranobuilder script is based on KAG, I want to make sure the current KAG parser is more stable.

So, I added a new parser based on KAG Script Tree Generator. It is a KAG script tokenizer for Script Tree Explorer.

This parser is significantly slower than the one I created. But I think It can parse accurately. So you have the options to switch between the parser on the Options menu. Please try it out. But please take note that you must use the same parser when you export/inject the project with the parser you’ve used when you created those particular projects.

Make the developer tools slightly better place

In order to make console log a more comfortable place to visit, In this version I cleared the console log from false warnings. I also got rid of the unnecessary sourceMap on all module nodes.

SourceMap tends to give a lot of false warnings in the console log. There are certain settings in the developer tools to hide these warnings.

Some nasty warnings from Google's official Cloud Translator modules

I want to fix this from the core of the problem.

So I scrubbed out all the js & css scripts in the application from this source map. The result is a slight increase in performance, especially for those of you who are using the Developer version.

You can update your Translator++ to Version 3.4.15 from auto-update.

Cheers

Comments

Jeress

Is there a way to automate clearing specific rows? I have a number or rows that start with \picn that need to be cleared and I either need to translate all but those ones or clear them from the current translation.

strife2cloud

I usually tag them. You can search for \picn and then tag all the results (I use red) and then when you export blacklist red tags.

autonomous spaghetti

Hello, I updated to the latest version (3.4.15), but it has a fairly large issue with the Search feature. - When having multiple windows of Translator++ open, it is not possible to open a search window in more than one of them at a time. Trying to do so will make the search feature not work at all until restarting the software. To reproduce, (1) open project A and project B in different windows of Translator++. (2) Open the search window with project A. (3) Try to open the search window with project B. The window will not open, and will not open even after closing project A's search window. Additionally, I found the ability to open more than one search window simultaneously helpful. But this behavior has been removed in 3.3.30. With both of these issues, I'm reverting back to 3.2.23 for now.

dreamsavior

Thank you for your report. I can fix the search window for multiple instance of Translator++. But why do you need more than one search window?

autonomous spaghetti

Sometimes while editing repetitive pieces of similar strings scattered around the project, I find it helpful to have the base string open in one search window while looking up the variable pieces of the string with another text window. For example, one project had pieces of text similar to "\C[4]x\C[0]を手に入れた!" which I translated to "Obtained \C[4]X\C[0]!". I wanted to check that I put the right item name for X and that I didn't break the color tags, so I searched for "を手に入れた" to get a full list of these messages. If I wanted to check an item name, I would search for it in another search window. Easy and fast. With only one window, I would have had to repeat the search for を手に入れた after every item name I checked. Rather annoying and time-consuming when there's more than a few of these lines to check. It's a rare situation and I can live without the feature (especially if I can work around it by opening a second Translator++ window), but it still was mildly helpful.

Anonymous

When I open the kirkiri game .exe file, the Japanese texts don't show up properly. They all show up broken (文字化け mojibake). Tried changing the Windows system locale to Japanese and opening again but it didn't work. Any clue as to how to get these Japanese texts display properly?

Anonymous

Thanks for the reply. I'm trying to insert Japanese texts into English version of the game. I have both language versions installed separately, so what I intended to do was open both versions on two different sessions of Translator++, and then copy&paste the Japanese texts into the English game. But when I open up the Japanese version, the texts are broken.

Anonymous

For reference, here's the screenshot: https://imgur.com/lxvarHy

dreamsavior

Your game is scrambled. You can provide Translator++ with the original format of the game. Or you can use tool like KirikiriDescramble to unscramble the script. Download the tool here : https://github.com/arcusmaximus/KirikiriTools

Anonymous

Hi, So I'm in the process of trying to translate a renpy game but every time I load it into translator++ I get this message when I try to open the game : [code] I'm sorry, but errors were detected in your script. Please correct the errors listed below, and try again. File "game/galerie_chapitre24.rpy", line 7: Line is indented, but the preceding tag statement does not expect a block. Please check this line's indentation. add "gui/menu_chapitre2.jpg" ^ File "game/galerie_chapitre24.rpy", line 26: Line is indented, but the preceding tag statement does not expect a block. Please check this line's indentation. add "gui/menu_magazines.png" ^ File "game/galerie_chapitre24.rpy", line 48: Line is indented, but the preceding tag statement does not expect a block. Please check this line's indentation. add "fondcolinfiche.jpg" ^ File "game/galerie_chapitre24.rpy", line 62: Line is indented, but the preceding tag statement does not expect a block. Please check this line's indentation. add "fondhanielfiche.jpg" ^ File "game/galerie_chapitre25.rpy", line 7: Line is indented, but the preceding tag statement does not expect a block. Please check this line's indentation. add "gui/menu_chapitre2.jpg" ^ File "game/galerie_chapitre25.rpy", line 26: Line is indented, but the preceding tag statement does not expect a block. Please check this line's indentation. add "gui/menu_magazines.png" ^ File "game/galerie_chapitre25.rpy", line 48: Line is indented, but the preceding tag statement does not expect a block. Please check this line's indentation. add "fondcolinfiche.jpg" ^ File "game/galerie_chapitre25.rpy", line 62: Line is indented, but the preceding tag statement does not expect a block. Please check this line's indentation. add "fondhanielfiche.jpg" ^ Ren'Py Version: Ren'Py 7.3.5.606 Thu Apr 29 07:17:53 2021 [/code]

Anonymous

Thanks for the help. The descrambling worked fine. Now I can read the Japanese texts properly. But there's been another problem where I can't inject translations. When I start inject/apply, the process doesn't end and continues forever. The "processing" bar keeps moving with the message "Parsing data. The window will appear hang sometimes. That's normal!" above it. The procedure gets stuck on the file "wuvorbis.dll" and doesn't progress any further. Any clue as to why this may be happening?

Jeress

Thank you, I was messing with tags but didn't think about that.