Megasquirt Support Forum (MSEXTRA)

Hello,

While I was working on MS3 string translations, I found a potential BUG in MS3.ini files.

In MS3 Format 0566.05 Line 5241 : There are quotes inside the string. It's maybe not important when using TS in English. But from what I guess this can be a problem when using TS translation engine as this one seem to use Quotes to separate strings.

Thanks,
Manu

Yes that's a bug. I would have thought that TunerStudio should warn about it.

James

Thanks,

Manu

Hi Phil,

while I translate MS3 sentence to French language I found some errors, the biggest one is describe below.

But I also found some limitations in the translation engine that lead in an inaccurate translation :

1 - It's case sensitive and that lead in many "double" strings in the database. It add many works in translations that can be avoid if TS wasn't case sensitive.
2 - The big problem is that TS match sentences. IMO this is not the better method to operate because MS firmware use similar sentences for many windows that, in French, can't be used like this. An accurate translation need to access each string in the window it belong to gain sense.

My thought is that rather to depend on sentences, TS translation engine will be better if it depend on labels. This way we can do accurate translations that match the field function rather than the sentence.

Best regards,
Manu

A large majority of the text to be translated comes from the ini files. Without changing the ini's a lot there isn't a much we can do to change the way it works. It key's off the string as it is defined in the ini file.

Now for the translations from text in TunerStudio, there are 2 types:
- Static labels
- Dynamically generated strings.

TunerStudio is essentially leveraging the translation engine for the ini files to handle the static labels. The Dynamically generated strings do not have a proper solution and are doing the best they can with what is there.
Ideally the text would be pulled out to external bundles with tags for the dynamical components.
Putting in a proper solution for the dynamical text has been on the todo list for many years, but only so many hours in the day and a continuously growing todo list.

Now the idea of keying non-case sensitive would probably not be too bad. There could be some negative repercussions, but probably more good than bad. Or perhaps let it 1st check for a case sensitive match, if not found go for case insensitive.

Hi,

jsmcortina wrote:Yes that's a bug. I would have thought that TunerStudio should warn about it.

James

It will be useful to correct it in the current archive since this is the actual stable firmware and that it will last for months. Also change the TS downloadable .ini at server side will be good to.

Thanks,
Manu

Manu wrote:Hi,


It will be useful to correct it in the current archive since this is the actual stable firmware and that it will last for months. Also change the TS downloadable .ini at server side will be good to.

Thanks,
Manu

I have updated the ini files on the server.

Thanks

This was fixed in CVS a long while ago, so will be included in the next beta.

James

Sound good