Tip:
Highlight text to annotate it
X
Click on Settings and configure XUITT. Other STEPS will use the information stored here.
Add your own devIcon.png, preview.png. Enter your name, choose your language.
Choose a default folder
Use the slider to define the pause intervals. Slow machines need a higher value.
The database management form has all the functions needed to edit your database.
For example importing an old database/translation.
If you enable Skin specific, all data in the xls file will be saved under that name. This might be useful if you would like to have separate
translations for each skin.
The file will be imported and verified if the data is correct. If it is Proceed button will be enabled and you can update your database.
You can also verify it yourself by selecting Update and the same parameters as before.
Now that we have a database with some translations let's start with STEP 1.
XZP consists of different steps. 1. Select XZP file
2. Choose where to extract this file Also known as Skin folder in the Settings
This folder is very important as the contents of it will be used to create the translated XZP file!
3. Each XUR file will be opened with XUITool and saved as XUI file.
As you can see this happens fast because the pause value is set to 1. If it gets stuck somewhere you'll need to increase that value.
A dual core does the job fine with pause value 3 for example.
As you see I'm not interrupting the process. I was even holding my breath! Just let it finish.
Don't check your emails. Don't surf in the internet, just let it be.
We are almost there.
4. Each XUI file will be imported as a new table.
A temporary table with strings found in this new table is filled with and values.
After importing all XUI tables it performs a check:
The first line of each XUI table must be:
Skin.xml and MenuSettings.xml are imported as well. The Translation table will be filled with all strings found.
STEP2. Select the source language and the language you want to translate it.
For this tutorial I'm using the previously imported database labeled as Default F3.
You can enable additional functions. If you're lucky the missing counter will decrease...
I don't recommend using the Google translator to do your job. It might help with some accents etc. though
You'll see what Google is translating at the bottom of the form. In the next step we'll be able to filter these translations.
STEP3 Translate, filter, capitalize etc.
While typing you'll see how much space you are using. Try to keep it as short as the source language.
See? Giving a good example...
Have you noticed the spaces in the source language? There is a function to copy those spaces for our translation.
Press F3... et voilĂ !
If some texts were not translated with Google before you can try it manually.
This function includes the copy spaces function from before.
There will be some texts that Google will not translate.
This filter shows all records were the translation is bigger than the source language.
This filter shows all translations done by Google in STEP2. The copy spaces function is missing there.
But you can execute this function for all records. I recommend doing it at the end of your translation.
Capitalize is another useful function. You have two options:
You can Capitalize All Words, or just the First word.
Just the first word...
And All Words...
STEP 4 MenuSettings.xml
All translations are taken from previous form. You can edit them manually. But remember,
each time you open this form it takes the strings found in the Translation table.
STEP 5 Skin.xml
By default it uses original skin name + to language. And for Author: original Author + translated by + user name.
You can change the preview.png picture and the devIcon.png picture. They are both taken from your Settings.
Or you can use this stylish XUITT icon and declare yourself a fan of this app...
Noooo! Use the XUITT icon!
Yes we know that already don't we? The preview and icon picture can be saved in the settings...
STEP 6 Create translated XUI files
You can choose between saving the translation skin specific or
overwriting existing translations in the database (not skin specific) with this new translation.
Another option is to adapt field width to translation. This is experimental and needs more tweaking. Not suited for some skins.
You can include your translation as xls in your XZP file. An easy way to share it with others.
The default setting for the XZP file is SkinName_Version_ToLanguage_XUITT.xzp.
Next we need to select a destination folder.
Remember, the contents of the Skin folder (the one we created in STEP1 - UNPACK FOLDER) will be used to create the XZP file.
Once you have all set, click on proceed. 38 tables to go!
The export log shows the progress.
In the end you should see. 38 XUI/XUR files generated as there are 38 tables to translate.
If a XUI file was not converted to XUR you should see file.xur > error.
Skin.xur is a big file and takes some time. Please be patient...
Finally!
MenuSettings.xml and skin.xml are created as well.
devIcon.png and preview.png (translation.xls) will be copied to the export folder and then it will create the XZP file (if selected)
Done! Let's see the export log.
Looks like all went as planned...
Now let's see the export folder with the generated files.
This file contains the translation we used to create the translated XUR files. It has been included in the XZP file as well.
Our customized devIcon.png and preview.png.
skin.xml with Skin Name, Author and some translations. Unfortunately only X-ANSI supported.
And the MenuSettings.xml file with some translations as well.
If you must change something just recycle the previously imported xui tables.
Select the languages, database options and there you go.
Change whatever you need to change in STEP 3/4 or 5 and do STEP 6 again.
XUITT supports multilanguage menus/forms! Thanks to all translators!
Subtitles by Keyser - realmodscene.com