It can be done auto-replacement, but you should look at each replacement before doing this, you may replace some neccessary space.
I'm going to do some work now, after that, I'll be working on a patcher.
EDIT:Yeah, auto-replacement should work, since most of cases are " 's " and " 't "
Last edited by Tidusnake666; 10-31-2011 at 11:25 AM
Ok, so that's why there were 0x8140 after words with apostrophes... (I was quite puzzled by this.)
You should note that the option '-P' of d4tool is precisely meant to handle those cases by automatic substitution. Of course, I don't know whether it is enough to solve all problematic cases. The '-P' option is meant to be used with the 'patch' action, and it sets $punctuation_heuristic to true, which in turn is used in this function (called on all strings written in the dat file):
Well, the "postfixed apostrophe" is actually a SJIS space character, but I didn't notice this when I was writing this function. ^^;
You may want to add new automatic substitution rules, such as "s/HP SP/HP\/SP/", to put back the '/' which should be in the Sardine description, for instance (well, this can simply be done by hand, so it is a stupid example).
Here is an exhaustive list of item descriptions automatically corrected when using '-P' when patching:
I have to check if the ? ! or ( ) and % are displayed correctly with our new script. If they are alright I only have to replace the apostrophes (with the script or via auto pasting). I'll put the / by hand. If everything works we'll have nice looking items, magic, skills, descriptions etc.
It's not a lot to edit by auto-replace, so if you won't manage to do it by script, there's not alot of work to do manuall (or, let it call, pseudo-manually).
Also, I thought about SOUNDS and decided that that piece of my work should R.I.P, since the later solution (talk.dat patching) is far more better.
Need any words on EBOOT translation progress, maybe we'll release something like "pre-beta" as soon as we will correct those "problematic" files
Tobster, you can just do the correction work, all those "glyphication" can be done by me, if you're busy. If not, be sure to use full command with "-k PRESERVED_GLYPHS -x EXTRA_STRINGS" and use file from this attachment: http://www.ps3news.com/forums/ps3-ha...tml#post393895
EDIT: Oh, and just a working check (if Tobster wants to glyphicate files):
I have redone all of our translated files ('t 's 'll 've and / ) and made a test with a "glyphed" mitem.dat for the items. It looks fantastic: No double spaces and all characters are shown correctly (even " ). Big Thanks to our team hackers for making this possible.