robins

i found there are some *.xtt files in :\flash\

is there a way to edit them so that NXE as well as Freestyle dash support more charset?

i notice some of the text strings in default.xex use font from arial.ttf but others just use the console font, i guess should be the *.xtt files as shown above

thanks!

RacerX, can you upload to a different share site?as i mentioned before, it's very difficult for me to download stuff from mediafire. thanks!

Glad you figured it out another zip that might help you out to skin faster... the xui files are just xml files so you can edit these in Visual Studio or notepad if you want

(Thanks c0z for pointing this out to me a few weeks back )

hi murf, both keyser and i are looking for a method to translate the game catagory titles(Xbox 360 games, xbox classic games, etc) located in skin.xml file(check keyser's thread: http://www.realmodscene.com/index.php?/topic/188-skinxml/#entry708). but it seemed that xml file only support ansi charset, which means it wont support languages with other charset. your comment gave me a strong feeling that it was not controlled by xex but the skin itself. do you have any idea on that?

congratulations keyser! great tool!

hey op, i love your creation, I did a search in xbox360iso but couldnt fing it, can you pm me the link?thanks!

first of all, F3 is great and i cant wait for RXE...

here is what i found,

username and password prompt window for Xlink KAI login display the same message: Xlink Username/Enter the Xlink username...(if i recall correctly).

i found it when i chinese hacked the xex file. i think the 2 scene call out the same prompt window...

and i believe the previous releases have the same issue.

Forgive me if this shouldn't be here,,, but murf your skin is great, are you working on any new skin for F3?

scan path issue solved. Select Directory is a mystery...

The Hex(Original UNICODE) to HEX(translated UNICODE) function does the following

ADR 0

REPLACEALL 4F 00 70 00 65 00 6E 00 20 00 54 00 72 00 61 00 79 00 00 BY 5F 39 51 FA 51 49 9A 71 00 00 00 00 00 00 00 00 00 00 00

The Hex(Original ASCII) to HEX(UTF-8(translated UNICODE)) function does the following

ADR 0

REPLACEALL 4F 70 65 6E 20 54 72 61 79 00 00 00 00 BY E5 BC B9 E5 87 BA E5 85 89 E9 A9 B1 00

In my screenshot it is still wrong. I don't know why. I just find it curious that copying arial.ttf without letting F3 know to use that instead of the xpr file should work. Maybe you are luckier. Let me know if the xex file is correct.

The GUI must still be finished but once this is done you'll be able to test it yourself

keyser,

1. unicode to unicode, original hex should start from 00, so REPLACEALL 00 4F 00 70 00 65 00 6E 00 20 00 54 00 72 00 61 00 79 00 00 BY 5F 39 51 FA 51 49 9A 71 00 00 00 00 00 00 00 00 00 00 00 00

2. utf8 to utf8 is correct, but there is a little problem for UTF8 Open Tray, if you use 4 Chinese charactors to replace the original string, there will be no separator(00) between the last code B1 and the successor code, then on the console you will see 弹出光驱+unreadable characters instead of 弹出光驱. my solution is use 3 chinese charactor for this specific Open Tray

I translated the default skin and also the xex into Chinese

Then I found I can't save scan path, add button is there but save is gone, I noticed delete and save both located on x button and should switch if work properly(with original xex),

i also do a clean installation but the problem persists,

Did I miss anything? I didn't use xuitt to hack xex because it doesnt support Unicode yet, for those who are using a Spanish xex hacked with xuitt, do you have the same issue?

Another minor issue, at the path manager path scene, there is a 'Select Directory' button, I translated it to Chinese but it still displays English, and there is no such string in xex, I notice the Spanish version has the same issue, don't know why,

Exactly, skin.xml would be the last file we have to deal with

Superb,,Keyser,,can't wait

Perfect robins! Thanks a lot! Yes, it was a font problem then. As long as I can't continue working on GaDaBaMa for FSD3 I'll concentrate on XUITT.

I'll go through the whole code and make the necessary changes to make it UNICODE compatible - I hope to have good news by the end of next week!

Keyser, great great!

I already made a Chinese xex but don't know if all the strings were translated. Hope the new xuitt will make it easy, can't wait:) maybe I should release a beta to public for testing...

@keyser

Open Tray is a very good example.

here is the hacked xex i made for you to check. testopentray.rar

you can find what i did to it.

i translated 2 strings for default.xex, one is big endian unicode Open Tray, the other is the ASCII Open Tray. replaced with 5F3951FA51499A71 (hex for big endian unicode 弹出光驱) and E5BCB9E587BAE58589E9A9B1(UTF8 for 弹出光驱) respectively

on my console, if i use the default font for F3, it will display like this

if i use the font i uploaded in the previous post, you will see this

now it's your turn, i am waiting for the unicode supported xuitt...

@ robins:

For example 弹出光驱 is big endian unicode _9Q.QI.q or hex 5F3951FA51499A71

I can create 5F3951FA51499A71 but F3 shows always _9Q.QI.q and not 弹出光驱. I thought this is a font problem ?

How did you get it working?

keyser, not sure if that's due to the font. rename the font i upload to arial.ttf and put that under media\fonts\

arialuni.rar

let's take Open Tray as an example. hex for Open Tray is 004F00700065006E00200054007200610079 (big endian unicode)

chinese translation is 弹出光驱, hex for which 5F3951FA51499A71(big endian unicode)

replace 004F00700065006E00200054007200610079 with 5F3951FA51499A71 (as you know, add 00 for the shortage).

for those ascii strings, replace them with UTF8.

worked great here, i believe you are almost there.

Robins, thanks for the translation btw. I've started the code several months back for unicode before going again to the hospital.

Don't remember very well what went wrong, but I think it was because of not using Arial unicode.

There are a lot of strings, I've done some research with IDA Disassembler but not all texts are shown. Some are for debugging purposes I guess.

So I just write them down once I come across them. Some are in unicode some in ascii other in both formats. Some should not be translated otherwise you'll get a black screen. These have FALSE / FALSE. I've used an additional field (nulls), as it seemed the only way to include some strings that appear more than once but should only get translated once. The script.xsc file used in XUITT is basically a search and replace script for xvi32. It searches for all instances if a start address is not given.

Here is my file (strings) I use for XUITT.

keyser, they are using big endian unicode.

Some texts are found in the SKIN file default.xzp.

But other texts are HARDCODED in the xex file (default.xex)

If you want to change texts like Open Tray, Delete stuff etc. you will have to hack the default.xex.

I don't know if you're using XUITT. But there is an option to hack default.xex. Depending on the language you're translating it may not work.

UNICODE is not supported for the hack.

Some texts will be still missing though, it was released yesterday and I didn't had any time to look for those and to include them in the database file.

Edit: Here and here you'll find more info about the problem/process.

keyser, happy to track you down here, lol. again i do hope you can make xuitt support unicode.

question: how to capture the strings hard coded in xex? you mentioned there were 100+ strings need to be translated, but acutally i sorted 200+ strings and i know there are more... what i did is just decrypt xex and open it with winhex and do search....