Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

arabic support #1

Closed
abuali129 opened this issue Jul 10, 2015 · 4 comments
Closed

arabic support #1

abuali129 opened this issue Jul 10, 2015 · 4 comments
Labels

Comments

@abuali129
Copy link

as it mentioned the arabic should use UTF-8 Encoding
but when I try to do it that way after repacking I get question marks instead of the letter I wrote in arabic.

I unpack .subp
edited .xml
repack the .subp using the .xml
unpack .subp again to double check
all thing I translated is shown as ??????? ???? ??? ????

@Atvaark
Copy link
Owner

Atvaark commented Jul 10, 2015

If I remember correctly picking Arabic as the subtitle language isn't officialy supported by the game. There are Arabic bitmap fonts in the archives, but since you can't pick Arabic in the menu the game will continue with the Latin bitmap and fail to look up the Arabic glyphs/characters.
What could work is replacing the Latin font files with the Arabic ones.

@abuali129
Copy link
Author

yes that right, but I didn't even came to that phase, I'm still on editing .subp but with no luck

@abuali129
Copy link
Author

this is after editing xml
http://i.imgur.com/HlzP1Ej.png

this is after repacking .subp and unpack it for double check
http://i.imgur.com/c3r3UHC.png

the characters encoding in xml is not supported by SubpTool? is that the case?
I tried punch of different encoding but all leads to same result

I will take a look on how PES 2015 arabic files coding looks like, it uses fox engine too

@Atvaark
Copy link
Owner

Atvaark commented Jul 11, 2015

FoxEngine.TranslationTool v0.1.3 should use the encoding specified by the language option (-ara in your case) instead of of the ANSI codepage of your system.

That should fix your issue.

@Atvaark Atvaark closed this as completed Jul 11, 2015
@Atvaark Atvaark added the bug label Jul 11, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants