- Jan 4, 2017
- 3,399
- 2,439
Used powershell to condense all the lines to one, so if the translation programs need a file that has the edits on one line you should be able to use this.
For which version is this? v1.06 or v1.08?Used powershell to condense all the lines to one, so if the translation programs need a file that has the edits on one line you should be able to use this.
Not sure about others but I am still encountering the same issues. One other thing i noticed between your file and other auto translated files is that there are no spaces outside of text within quotation marks in the auto translated files for translator++. Your file has spacing between brackets and other elements. Again not sure if it matters but it is the only thing I can think of that is causing the issues.Whatever the one in the OP is, its the one Blackjack was working on originally and where he gave me the the translation file.
Could be the format I did to make it easier to read. Never used these before so didn't know you can't have spacing in them. I'll see if I can condense the format again.Not sure about others but I am still encountering the same issues. One other thing i noticed between your file and other auto translated files is that there are no spaces outside of text within quotation marks in the auto translated files for translator++. Your file has spacing between brackets and other elements. Again not sure if it matters but it is the only thing I can think of that is causing the issues.
Any luck on your end? I tried with notepad++ and was able to remove all spacing to include those inside dialog quotes. Hopefully if this works it will allow your edits to be loaded.Could be the format I did to make it easier to read. Never used these before so didn't know you can't have spacing in them. I'll see if I can condense the format again.
Follow-up tried to load the one line file with all spaces removed, no luck but it did drop the size from 7MB to 3MB. Did also notice that the references using Japanese characters in your file use weird characters instead (CSS_IMAGE:戦闘立ち絵表情睨み from a quick machine translation I did and your file has CSS_IMAGE:戦闘立ã¡çµµè¡¨æƒE¨ã¿). Imagine there are some corrupted lines causing Translator++ to freeze up. Can you provide the original file used? I would like to look at it.Could be the format I did to make it easier to read. Never used these before so didn't know you can't have spacing in them. I'll see if I can condense the format again.
Haven't gotten back to it yet, I used powershell to clean up the lines somewhat but it still leaves a couple of spaces or tabs in there, even though they should be removed. Though taking a deeper look into the file I noticed it changed the type into those weird characters. Tried using the json formatter to compact the lines but it chokes on something in the middle of the file, or it could be the length. I'll see if I can come up with something,Follow-up tried to load the one line file with all spaces removed, no luck but it did drop the size from 7MB to 3MB. Did also notice that the references using Japanese characters in your file use weird characters instead (CSS_IMAGE:戦闘立ち絵表情睨み from a quick machine translation I did and your file has CSS_IMAGE:戦闘立ã¡çµµè¡¨æƒE¨ã¿). Imagine there are some corrupted lines causing Translator++ to freeze up. Can you provide the original file used? I would like to look at it.
The problem is not in lines or spaces - as long as json is valid it should be able to read.I ended up putting it into a json beautifier so I could make sense of the lines while editing the text
Still learning / playing around with translator++, how did you find this one error?The problem is not in lines or spaces - as long as json is valid it should be able to read.
There is one newline error on the line 94542 - "\" instead of "\n", which makes json invalid - found by validating in JSONLint.
Adding "n" after backslash fixes this - i was able to open corrected file in translator++.
View attachment 719096
View attachment 719114
copied the file's content to online json validatorhow did you find this one error?
for which game version?the attached zip has the new data files if you want to use this translation
Ah didn't notice that, I'll make that change locally so its there. Probably from when I went back and edited somehow backed over it.The problem is not in lines or spaces - as long as json is valid it should be able to read.
There is one newline error on the line 94542 - "\" instead of "\n", which makes json invalid - found by validating in JSONLint.
Adding "n" after backslash fixes this - i was able to open corrected file in translator++.
View attachment 719096
View attachment 719114
I have been using v1.06. Not sure if that is the latest version.copied the file's content to online json validatorYou must be registered to see the links
it shows where errors are
for which game version?
I posted 1.08 on the previous page.I have been using v1.06. Not sure if that is the latest version.
The word is オリクト (Orikuto).I am encountering the term Olitic used throughout. Is there a better translation for this (i.e. demon, devil, monster) or leave it as is?
Olitic was the most common term in the original file, there were two or three other spellings, I generalized on that one and replaced the other usages throughout. It seemed the closest to what was there, and having a name for the enemy fit better with the story. Finally seeing it in game some things still don't look right and there were lines I had thought were cut down that still weren't, thanks for doing that I did want to have a check on the editing to see how it looked. Oh well.Will shift my efforts to 1.08 then, thanks for the heads up.
In my attempts to get better with translator++ I using this as a test bed to learn from. While trying to incorporate word wrapping I am encountering the term Olitic used throughout. Is there a better translation for this (i.e. demon, devil, monster) or leave it as is?