Portuguese Translation

[Dudix]

Hello,

I'm from Brazil, and interested in translating Tuner Studio to portuguese.

Is it possible?

[LT401Vette]

It is very much on my road map to make it multilingual, but I'm not quite there yet. There are MS'er from an awful lot of different countries and languages.
I don't have most of the verbiage externalized so it can be translated. Naturally as more people request it, I will move it up the list. So speaking up is good...

[jsmcortina]

Is a big part of the problem the fact that a lot of the words are within the ini file though? So it is (historically at least) the firmware writers who are creating the language?
That also the brings up the MSQ format because the verbal settings are saved - how best to get around that? We could I guess get the ini files translated and perhaps TS could have ms2extra-2.1.0.ini.en and ms2extra-2.1.0.pt etc and xref between the two for MSQ loading ?? i.e. if an MSQ is saved in English then the English ini file is used to convert into raw data, then the natural language ini file is used for the user interface?

e.g. Here's a menu fragment of the ini file in English:
dialog = triggerWheel, "Trigger Wheel Settings"

topicHelp = trighelp

field = "Trigger wheel arrangement", spk_config_trig2
field = "!Trigger Wheel Teeth", triggerTeeth
field = "!Missing Teeth", No_Miss_Teeth, {spk_config_trig2 != 2}

All of the words in quotes can be immediately translated with no harm and would not break TS in any way.

Here's a data definition section of the ini file in English:
spk_config_spka = bits , U08, 988, [0:0], "JS10", "D14" ; ( 1 byte )
spk_config_camcrank = bits, U08, 988, [1:1], "Crank wheel", "Cam wheel"
spk_config_trig2 =bits, U08, 988, [2:3], "INVALID", "Single wheel with missing tooth", "Dual wheel", "Dual wheel with missing tooth"
spk_config_trig2l =bits, U08, 988, [4:5], "INVALID", "Rising edge", "Falling edge", "Rising and falling"
spk_config_resetcam = bits, U08, 988, [6:6], "Cam", "Crank"

As soon as the words here are translated, then MSQs created in another language will not work without special coding in TS, although it might not be too hard?

For MS2/Extra there are only two (nearly three) "release" versions of code, so only these would need translating. I think translation is a good idea if it can be achieved with MSQ portability.

James

[LT401Vette]

Is a big part of the problem the fact that a lot of the words are within the ini file though?

Excellent point, but it is also a big part of the solution. The common solution for applications is to pull all verbiage out of the code and put it in ASCII files with a reference identifier for each unique string. Then place those language specific files in a sub folder with the language code, i.e. en.
So if I were to do this with TS, I would just need to pull all the english out, but I can't really translate it as the only languages I only know are English, Java, C and C++
So it would be multilingual with the first language being english . This is the effort I am looking at.

This presents the problem you are looking hitting on, even if I do that an awful lot of the important text is in the ini file. So you would still have mixed languages unless the ini is translated too. So with so many ini's....

But this also presents a good opportunity, the ini file verbiage is already externalized and easily edited by just about anyone. With a large chunk the important verbiage in the ini, that would get a good step there. I can easily put in support for different language ini's.

As for with msq compatibility, that get's a bit tough, but it is only the bit fields with string values that would be impacted. I think everything else is fine. Personally I would prefer if the numeric values were saved to the msq's instead of the string values, then this wouldn't be a problem, but that would break MegaTune compatibility..
However, I could save the numeric values elsewhere in the msq where MegaTune doesn't read. Then it could be compatible with Megatune in English, but any language in TunerStudio.

[molak]

Excellent point, but it is also a big part of the solution. The common solution for applications is to pull all verbiage out of the code and put it in ASCII files with a reference identifier for each unique string. Then place those language specific files in a sub folder with the language code, i.e. en.

Take the verbiage out of the code, do the english file. Based on the english file i can do the spanish version...

Is not possible to make TS show verbiage in X language but save it in english ?

[jsmcortina]

Excellent point, but it is also a big part of the solution. The common solution for applications is to pull all verbiage out of the code and put it in ASCII files with a reference identifier for each unique string. Then place those language specific files in a sub folder with the language code, i.e. en.

Take the verbiage out of the code, do the english file. Based on the english file i can do the spanish version...

Is not possible to make TS show verbiage in X language but save it in english ?

That's similar to what I was thinking - if TS can use the English.ini for loading into internal memory and saving to disk and then use natural-language.ini to display the memory contents, then MSQs could be shared internationally, but the user could work in their natural language?

I say this without any knowledge of the internals of TS.

James

[molak]

Any update on this ??