KyleFan Posted July 29, 2021 Posted July 29, 2021 Hi everyone! Freshly new member here, sorry if I haven't posted this into the right thread. I have a difficult question I couldn't find the answer to on my own. I like doing translations to my language and I had no problem writing in string files. Now I encountered some texts in a mod that show up by a script made in BehavEd using the 'print' command. I had no problem writing my translations in there, everything was fine. Then I opened up Jedi Outcast and when the text shows up, the accented characters are missing. For example if I write "hétvégi üdülőhely" in BehavEd, in-game it is shown as "h.tv.gi .d.l.hely". I checked if the text got messed up by saving it to .ibi but it stays correct. So the problem has to be with the game itself. I can't figure out what because it never had a problem displaying accented characters with using strings text. So the game has these characters in the fonts. Something else is wrong. I know that English speakers might never encountered this issue because English doesn't really have accented characters, but I hope there is at least one person here who knows about this and has a solution. It really bugs me that I can't figure it out. Any suggestions would be greatly appreciated!
Lancelot Posted July 29, 2021 Posted July 29, 2021 15 minutes ago, KyleFan said: For example if I write "hétvégi üdülőhely" in BehavEd, in-game it is shown as "h.tv.gi .d.l.hely". My guess is that the English text is not compatible with accented characters. As far as I know, those aren't even included in the English files. You could pick another foreign text file that uses those characters and replace the lines with the ones you've written. Then load that file in the game and see if those characters appear.
Solution mrwonko Posted July 30, 2021 Solution Posted July 30, 2021 I suspect that scripts don't support non-ASCII characters. I think you can reference strings in the print statement (using an @ or something?), that will likely fix it?
KyleFan Posted July 30, 2021 Author Posted July 30, 2021 Thank you for the help, guys! You got it right, mrwonko. It was the @ symbol. I had to experiment with it for a while to make the reference work. It turned out it is: @FILENAME_REFERENCE It works perfectly. Thanks again! mrwonko and Asgarath83 like this
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now