XStudio is provided in 6 different languages:
The localization files are accessible outside of the code to give all the flexibility to update it independently from the code.
They are all licensed under LGPL and their sources are provided as such.
Even though we try to maintain constantly those localization files, some may be not perfectly up to date and may require some small polishing. If you see in the GUI some labels starting with a question mark, this means those terms have not been yet localized in your language and require an update.
Speaking about localization, there are 4 main things you can do:
The localization file to update has a name similar to XSTUDIO_en_US (without any extension).
The file is encoded in UTF-8 by default and must be edited as such. We advise using Notepad++ to edit the localization files.
You'll need to edit the section at the right hand side of the '=' sign on each line.
When you're done with the changes, just send us a message.
We'll be able to include it in the standard distribution and very quickly deliver a patch version that will include your changes so that you can check everything's perfect.
To do that, just copy the English localization file (XSTUDIO_en_US), rename it using the appropriate standard "language symbol" (i.e. 'en') and country symbol (i.e. 'US') corresponding to the localization you need.
Then, edit the section at the right hand side of the '=' sign on each line.
When you're done with the changes, just send us a message.
We'll be able to include it in the standard distribution and very quickly deliver a patch version that will include your changes so that you can check everything's perfect.
Just copy the English localization file (XSTUDIO_en_US), rename it using the appropriate standard "language symbol" (i.e. 'en') and country symbol (i.e. 'US') corresponding to the localization you need.
Then, edit the section at the right hand side of the '=' sign on each line.
When you're done with the changes, convert the file to an ISO encoded file and add the ".properties" extension to the file name.
Then, you'll need to build the localization package and sign it before pushing it to your server:
- English
- French
- German
- Italian
- Chinese
- Spanish
The localization files are accessible outside of the code to give all the flexibility to update it independently from the code.
They are all licensed under LGPL and their sources are provided as such.
Even though we try to maintain constantly those localization files, some may be not perfectly up to date and may require some small polishing. If you see in the GUI some labels starting with a question mark, this means those terms have not been yet localized in your language and require an update.
Speaking about localization, there are 4 main things you can do:
- Contact us so that we update the missing terms
- Update the missing terms yourself and provide us with your changes
- Create your own language and request it to be integrated
- Customize a localization file and maintain it yourself
Contact us so that we update the missing terms
This option may take some time though.Update the missing terms yourself and provide us with your changes
You can also update the missing terms yourself by editing the localization file of your choice and provide us with your changes.The localization file to update has a name similar to XSTUDIO_en_US (without any extension).
The file is encoded in UTF-8 by default and must be edited as such. We advise using Notepad++ to edit the localization files.
You'll need to edit the section at the right hand side of the '=' sign on each line.
When you're done with the changes, just send us a message.
We'll be able to include it in the standard distribution and very quickly deliver a patch version that will include your changes so that you can check everything's perfect.
Create your own language and request it to be integrated
If your language is not yet supported, please send us a message to request it or you can generate it yourself.To do that, just copy the English localization file (XSTUDIO_en_US), rename it using the appropriate standard "language symbol" (i.e. 'en') and country symbol (i.e. 'US') corresponding to the localization you need.
Then, edit the section at the right hand side of the '=' sign on each line.
When you're done with the changes, just send us a message.
We'll be able to include it in the standard distribution and very quickly deliver a patch version that will include your changes so that you can check everything's perfect.
Customize a localization file and maintain it yourself
If your language is already supported but you'd like to customize some terms you can also do that.Just copy the English localization file (XSTUDIO_en_US), rename it using the appropriate standard "language symbol" (i.e. 'en') and country symbol (i.e. 'US') corresponding to the localization you need.
Then, edit the section at the right hand side of the '=' sign on each line.
When you're done with the changes, convert the file to an ISO encoded file and add the ".properties" extension to the file name.
Then, you'll need to build the localization package and sign it before pushing it to your server:
- Ensure you have an official (to be purchased on any security provider such as GlobalSign) public code signing certificate
- Create a jar file containing all the localization files
- Sign it using your certificate (you can use OpenSSL for this) and generate a localization_signed.jar file
- Publish this file on your server at the usual place
- If you still have the old localization, delete the localization_signed.jar file from the clietn's java cache and restart XStudio