- #Qubicle voxel editor tpb how to#
- #Qubicle voxel editor tpb code#
- #Qubicle voxel editor tpb download#
To make the tranlation process easier, keys are descriptive.
So, not all words found in a dialog are necessarily declared in its section, it might be declared before. the key WIDTH is used many times in Qubicle but has to be declared only once. Please note that keys only appear once in the ini files. All sections starting with DIALOG are words found in pop up dialogs. All sections starting with MENU are menu entries, so everything found under are menu entries of the File menu. I use sections only for organization puposes, and to give you an idea where to find a word. There are section headers like and loads of lines with key/value pairs like FILE = File. All ini files are regular Windows ini files, which work like this: There are two separate files, one for the ui and one for the quick help found in the status bar. Otherwise send the corrected files to supportminddeskcom. If you are familiar with Git make a pull request.If you like to test what you have done, copy the files to documents/Qubicle 3.0/, rename them to custom_ui_translation.ini and custom_help_translation.ini and proceed as described above.
#Qubicle voxel editor tpb download#
#Qubicle voxel editor tpb how to#
How To Correct Parts Of An Existing Translation
#Qubicle voxel editor tpb code#
Send the files along with the language code (e.g.Start Qubicle to test the changes you made.Translate values in the custom ini files.