Infernoplex Posted December 25, 2017 Share Posted December 25, 2017 6 minutes ago, marcus-beta said: in this case, Add-me on discord: Marcus André#0956 Sent request. Quote Link to comment Share on other sites More sharing options...
binaryfail Posted December 25, 2017 Share Posted December 25, 2017 (edited) @Infernoplex The codepage conversion warning probably means ahdprc is using cp936. You'll need to change it to 932 by editing the tool's source code and compile it again. The number shows up twice in the tool code. Character's names in this game are prefixed with %LF instead of %LC, so ahdprc wasn't picking them up. Again, that'll require editing the tool and recompiling. wpscrpt.cpp, line 50: change 'C' to 'F' wpscrpt.cpp, line 82: change "%LC" to "%LF" When the text is extracted, the character name will appear next to the line number within the script. Edited December 25, 2017 by binaryfail Infernoplex 1 Quote Link to comment Share on other sites More sharing options...
Infernoplex Posted December 25, 2017 Share Posted December 25, 2017 (edited) 1 hour ago, binaryfail said: @Infernoplex The codepage conversion warning probably means ahdprc is using cp936. You'll need to change it to 932 by editing the tool's source code and compile it again. The number shows up twice in the tool code. Character's names in this game are prefixed with %LF instead of %LC, so ahdprc wasn't picking them up. Again, that'll require editing the tool and recompiling. wpscrpt.cpp, line 50: change 'C' to 'F' wpscrpt.cpp, line 82: change "%LC" to "%LF" When the text is extracted, the character name will appear next to the line number within the script. Now that helps with showing the names in the .txt files Compiled it and tried to grab the text file with the new ahdprc. On ENG script I get to see the names correctly: JP script is fine as well: Thank you Also, changed the CP value from 936 to 932 in 2 places (from what I have seen, it pops out in 3 places, but in 1 of those 3 places it's already set as 932). Thank you for all of this great help ^^ ... By the way, is there a specific reason why there are duplicate lines like this? Edited December 25, 2017 by Infernoplex Quote Link to comment Share on other sites More sharing options...
binaryfail Posted December 25, 2017 Share Posted December 25, 2017 10 minutes ago, Infernoplex said: By the way, is there a specific reason why there are duplicate lines like this? The first line is there for reference. The second line is what you'll want to translate/edit, and that line will be filtered for insertion. Infernoplex 1 Quote Link to comment Share on other sites More sharing options...
Infernoplex Posted December 25, 2017 Share Posted December 25, 2017 Just now, binaryfail said: The first line is there for reference. The second line is what you'll want to translate/edit, and that line will be filtered for insertion. Ah, thanks for that info. That means I didn't have to edit the first line at all earlier, just the second one. The thing you mentioned earlier about line counts, if I, for example, have additional lines from the ENG release that I'd need to put into the JP script... does it work from the get-go by just adding the lines in this format like they are in the .txt files or would there need to be additional work done on BIN files? I remember you mentioned I'd need to pay attention to it, and I found out there are different line counts in scripts. Will there be a problem of some kind if I only simply add lines like that in JP script? Quote Link to comment Share on other sites More sharing options...
binaryfail Posted December 25, 2017 Share Posted December 25, 2017 You shouldn't add or remove lines in the JP script, otherwise the lines will fall out of sync with the rest of the script; voices and images would no longer match up with the text. Instead, you'll need to merge or adapt the translated text to fit within the confines of the original JP line. Quote Link to comment Share on other sites More sharing options...
Infernoplex Posted December 25, 2017 Share Posted December 25, 2017 3 minutes ago, binaryfail said: You shouldn't add or remove lines in the JP script, otherwise the lines will fall out of sync with the rest of the script; voices and images would no longer match up with the text. Instead, you'll need to merge or adapt the translated text to fit within the confines of the original JP line. Ah, I see now. Okay then ... That makes sense. Thank you very much for all your help Quote Link to comment Share on other sites More sharing options...
Veshurik Posted December 29, 2017 Share Posted December 29, 2017 Ой, Коносора на русском. Какая милота! Wow, Konosora in Russian. How cute! Quote Link to comment Share on other sites More sharing options...
Veshurik Posted August 23, 2018 Share Posted August 23, 2018 Eeeh... Dead? Вы решили умереть?.. Quote Link to comment Share on other sites More sharing options...
Lucky Itsuka Posted January 7, 2019 Share Posted January 7, 2019 On Thu Aug 31 2017 at 12:14 PM, binaryfail said: Here is a .bat file to run the compile. Should've had a makefile instead... Save this .bat and run it in the "src" folder. Their readme says to use MinGW with gcc 4.7.1 which I will agree with. The tool won't run correctly if it's compiled with newer gcc versions. set path=C:\MinGW\bin mkdir obj del obj\*.o for %%f in (*.cpp) do g++ -std=c++11 -O2 -fstack-check -fbounds-check -fstack-protector-all -Ilib -c %%f -o obj\%%~nf.o g++ -s -o ahdprc.exe obj\*.o -static -Llib -lprincess -lssp pause Did anyone know why i get this error? Quote Link to comment Share on other sites More sharing options...
Infernoplex Posted January 7, 2019 Share Posted January 7, 2019 (edited) 11 hours ago, Lucky Itsuka said: Did anyone know why i get this error? I vaguely remember having the same problem back in the day. I forgot how I fixed it, but I think it has to do with the compiler you're using to make the .exe out of the source code. Edited January 7, 2019 by Infernoplex Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.