Keyser
-
Content Count
216 -
Joined
-
Last visited
-
Days Won
16
Everything posted by Keyser
-
It should be under FSD3DataDatabasescontent.db Table ContentItems Fields ContentItemName / ContentItemDescription There is an app to handle/upload DLC and stuff "360 Content Manager" maybe you're luckier with that. Edit. It looks like you're using it already. Well then the USB transfer trick should work as well I guess.
-
XUITT 2.0.2 Added Polish GUI thanks to scynio Changed adapt field logic. Takes also note of font size! Fixed some minor bugs
-
Afaik it's already done that way. I think it extracts the name from the default.xex and when downloading covers/images from xbox.com it updates the name and description based on the TitleId. All this information is already stored in a database - sqlite database to be precise. Maybe this post can help you.
-
I think the webui might help you to change the names and descriptions of your games. Or else you can edit the database file manually for example with Sqlite Pro 2009 (freeware).
-
Here is an english translation of the skin (includes XLS file with translation). This skin was not tested on the Xbox 360. Voici une traduction anglaise du skin (fichier xls avec la traduction inclus) Ce skin n'a pas été testé sur Xbox 360. Translation file Sphinx_3.0_EN_XUITT_XLS.zip Skin file Sphinx_3.0_EN_XUITT_Skin.zip
-
I just finished this file which contains almost a full FR-EN translation. All english strings have been taken from F3 Default skin to allow a cross-translation in XUITT 2.0 to other languages! Some 40 strings were not translated because I was not sure of their meaning. I would need to install the skin to see where they fit.. I did the job as accurate as possible without testing the skin nor the translation. If someone wants to test it / retake it where I left be my guest. _______________ Je viens de terminer ce fichier qui contient presque une pleine traduction FR-EN. Toutes les phrases/mots en anglais ont été prises à partir du skin par défaut F3 pour permettre une traduction croisée en XUITT 2.0 pour d'autres langues! Environ 40 enregistrements n'ont pas été traduits parce que je n'étais pas sûr de leur signification. J'aurais besoin d'installer le skin pour voir où ils apparaissent. J'ai fait le travail le plus précis possible sans tester le skin ni la traduction. Si quelqu'un veut le tester / le reprendre où j'ai laissé n'hésiter pas. Edit1: updated to full translation/ maj - traduction complète myDatabase_FR_to_EN_Looping.zip Edit2: Here is an english translation of the skin (includes XLS file with translation). Voici une traduction anglaise du skin (fichier xls avec la traduction inclus) looping_3.0_EN_XUITT.zip
-
Thanks Sindyrello & rip88 for your updated translations. XUITT 2.0.1 released Changelog -Added Russian GUI thanks to MazheM , Cosmaty31 & Sindyrello -Added Czech GUI thanks to rip88 -Added new functions for Database Management (replace/complete DB) -Changed Filter off hotkey from ESC to F8 (gave errors)
- 81 replies
-
- 1
-
-
- Freestyle Dash
- Skins
- (and 2 more)
-
Great thanks! I'll update XUITT tomorrow with your GUI and send you the link and some instructions to verify it. I've included some explanations in english for the How to translate video tutorial. You'll find the srt file and more infos in the first post.
- 81 replies
-
- 1
-
-
- Freestyle Dash
- Skins
- (and 2 more)
-
To check if you have SP1 installed: -Open MS Access 2010 32bit -File -Help -click on Additional Version and Copyright Information You should see Access 2010 SP1 on top. If you receive a "The expected version of the product is not found on the system" error while trying to install Access 2010 SP1 then I guess it can have 2 logical reasons: 1) 32/64bit problem 2) Access 2010 is not installed in english If its 2) try downloading the service pack 1 in your language LINK Thanks Sindyrello for your translation. I'll update the ribbon and include Russian as language. Is this correct? руÑÑкий
-
Thanks JPizzle
-
There is no need to edit the file online. Just download it. File, Download as, M$ Excel xlsx :-D
-
You find the link to the xls file in the first post under How to contribute. Thanks
-
First beta released. Please report any bugs you encounter here. Thanks.
-
This sounds like the skin is meant for FSD2.2 and not for FSD3.
-
Thanks robins. 1) has been done and now it is correct I guess. For 2) That's a bit more tricky. Open Tray for example appears just once and although there is one for unicode and one for ascii, I think using 4 chars for one and 3 for the other is just too complicated. Thats against XUITT logic. I tried different settings but if you want to use 4 chars you'll have to correct the file manually. To prevent any 00 (separator) errors I limited the available translation space: From REPLACEALL 4F 70 65 6E 20 54 72 61 79 00 00 00 BY E5 BC B9 E5 87 BA E5 85 89 E9 A9 B1 to REPLACEALL 4F 70 65 6E 20 54 72 61 79 00 00 BY E5 BC B9 E5 87 BA E5 85 89 E9 A9 This way each string has at least 00 at the end. I'm afraid this will have to do it. Using Unicode is much complicated as UTF-8 because the char count in the translation form has no effect on the actual hex length. With UTF-8 it is easy to determine if you are using too much space or not. Realtime hex conversion while typing is out of reach. That would take too long. I've seen that other languages that used special chars should also be compatible now. For example hungarian: I'll clean up the database and send you the file for more tests. You'll be faster to find any errors than me learning chinese
-
Alright robins, I think we are almost there. The file contains all my work until now. I've translated all strings with google translator just to have some chinese strings. 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 CHINESE.zip
-
FILES 32/64bit Manuals Changelog Infos Credits STEPS Errors/bugs SUBTITLE FILE FOR HOW TO TRANSLATE FSD2/3 SKINS - YOUTUBE TUTORIAL XUITT_A2013_2.1.6.rar
- 81 replies
-
- 5
-
-
- Freestyle Dash
- Skins
- (and 2 more)
-
Is it possible to save this file in another encoding than X-ANSI? MenuSettings.xml for example can have other encodings. Is there any way to bypass this limitation? Or am I missing something here? XUITT 2.0 is almost finished and this would allow a perfect translation. Thanks
-
Lo siento, de momento ando muy ocupado actualizando la herramienta para hacer las traducciones de los skins. Una vez completada creo que será tan facil que cualquiera deberÃa de poder hacer sus propias traducciones. I'm sorry, but I'm too busy now updating XUITT. Once completed you should be able to easily create your own translated skins.
-
Thanks for contributing. A spanish translation of the default skin was already made by bocasecaman. If you would like to improve/change the translation I would start with his database.
-
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!
-
bocasecaman y yo solemos traducir los skins al castellano pero no los creamos. Los MetroStyle Skins son creados por HackLink, Freakazoid y idefix. Segun tengo entendido ya están a punto de caer para Freestyle 3. bocasecaman and I use to translate skins in spanish but we do not create them. MetroStyle skins are done by skinners like HackLink, Freakazoid and idefix. It looks like they are already upgrading them for Freestyle 3.
-
There have been some changes that I am not able to figure out without help. As soon as I get some informations about it I'll try to adapt it for GaDaBaMa.
-
@ 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? @ SPAM: XUITT does not generate any skin.ver file. Only skin.xml/menusettings.xml and all xui files are generated. I'm afraid I cannot assist you in this regard.
-
Charlito, do an export Database under Database Management to save your database. Rename your FSA_XUITT.accdr file to OLD_XUITT.accdr and copy this file into %LOCALAPPDATA%\SPIFFY360 This is my accdr database with F3 skin preloaded. Go to Database Management and import your database in your language again. I've done a spanish and an italian version with those files without freezes. Hopefully it works out for you too. 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. xex_Default.zip
