RPGMaker Trans 1.99 Fixed... Again

OK, I've updated 1.99 to fix the 'download a new release' problems. Again. If you need the 1.99 version, download it again and it should now work.

However, wierd bugs like this one is basically  the reason that I'm doing the version 2 as a near complete rewrite. The v1.x series are pretty much completely unmaintainable.

Status on 2.0 bugs: Currently being worked on. I'm still unable to reproduce them, but I'm relatively confident that locale issues are at play. I'm currently setting up some VMs to do proper testing etc.

Note: If you have issues with 2.0 at the moment, please let me know. I am planning to kill off the 1.x series as soon as I can, so I really do need to get all bugs etc ironed out.

EDIT: Link fixed. Sorry, my bad.

Bugs

Right, so two bugs that have popped up:

1) RPGMaker Trans 2.0 RC2 sometimes doesn't pick up a game
2) RPGMaker Trans 1.99 update checker has triggered for some reason.

If you need to use RPGMaker Trans 1.99 because 2.0 does not work, delete the config file before running 1.99. I'll try to post a fixed version of 1.99 as soon as I can.

RPGMaker Trans v2.0 RC2 Released

So that took a little longer than I thought it would... the blame for this lies solely with Disgaea D2.

New RC is out, and it should actually work this time.

There's a few known bugs, but nothing is a deal-breaker as such:

• Progress bar sticks at 99%, even after patching has completed.
• CLI mode is untested, but probably won't work due to bugs in either Windows or the Python implementation on Windows. Not sure which.

Link: Dropbox

RPGMaker Trans v2.0 RC1 Released

OK, so the new version of RPGMaker Trans, after months of delays, is finally almost here. I'm releasing this as a release candidate because simply, due to Windows-problems, I haven't been able to do the level of testing on this that I'd like.

So disclaimer: I only think this works. No testing on the windows binary has been done, other than to confirm it runs. No guarantees. If your computer grows green hair and teeth and proceeds to eat your cat, I'm not to blame.

EDIT: Pulled due to a crippling bug. An RC2 will be released as soon as possible.
EDIT2: There are more bugs in the Windows version that I thought. RC2 may be delayed until Friday, depending on how fast I can squash them.

Progress

Checking in with a progress report... Nothing amazing, but here's the run down.

• Translator core: 100% done.
• CLI Mode: 100% done (could be improved, but error reporting will handle the current problems)
• GUI Mode: 100% done
• Final Testing: 50% done

For those wondering about CLI (command line interface, useful for scripting and stuff), it will hide behind a --cli switch. Thanks to the magic of Python,  there is already fully documented command line help, so it should be pretty easy to use.

I'm wary of saying it, but unless something goes badly wrong, expect a release within a week.

EDIT: So I'm updating this post with progress as stuff gets done. Italics and strikeouts indicate changes.

Incidentally

For those wondering about VX support, I refer thee to this article.
.
Basically, VX support is 95% done. The problem that remains is parsing Ruby to pull the strings out of it. It's not easy; most of my attempts either don't get all strings, or fall into some endless loop. Currently looking at the rubylexer library, or possibly Topaz's lexer - not sure if either is particularly usable for my purposes... but hopefully I can work something out.

With a bit of luck, there should be a new version of RPGMaker Trans, with a shiny new GUI and stuff, by the end of this week. Make that by the 15th. Some problems came up. Why do I even bother setting a date? Soon.

Stupid Python Multriprocessing Daemonic subprocess not being able to have child processes...

Patch Format v3

This isn't the long awaited next version announcement, but just some notes on what the new patch format is going to be like, and a request for anything I've missed. Now that that's out of the way...

As translators no doubt know, there's a few problems with v2 of the patch format. In no particular order, I think these are the top 3:

1. Common strings to multiple files require multiple translations
2. Big files
3. No comments

At the very least, I'm aiming to fix all of these in the v3 format. 1) is already fixed (so no more translating "Yes" hundreds of times).  3) is almost done (suggestions on syntax? Currently there's a # COMMENT block, but that's not so easy to type...). 2) isn't started, but the plan is to have a couple of user definable variables which control how much goes into each file (one to control how big something has to be to be in it's own file, and one to control how many things to put into a single 'common' file).

Now: any translators want to suggest any other features that would be nice?