[Deepstar]

Hello guys,

at the moment i am assisting in a translation project for the whole SCP and some user-made campaigns of it.
I am working on the strings.tbl now, so i translate/correct all menus and options of this game. So no campaign specific changes.

Actually there seems to be, that some texts of the game are not covered by the strings.tbl.

Even i translated all entries, indivial textes in the menus are still in english.

I get the information from the person, who is responsible for this project, that there should be in total 1637 string entries according to the source code.
But the strings.tbl cover only 1539 of them?

Also strings 503-506 and 615-619 were not included in the strings.tbl after all. I have to add them manually, to fix some of the errors.

But even i added strings from 1570 to 1637 (higher than 1637 causes a crash) with a placeholder text in the strings.tbl, none of them affect the text, that still remains in the original language.

To be more specific, it concers some of the control options, that seems to be the last missing piece. Even i would like to know, for what all the other strings stands for .

I need the string numbers for a translation of following options:

"Glide when pressed"
"Toggle Gliding"
"Cycle Primary Weapon Firing Rate"
"Top Down View"
"Target Padlock View"
"Toggle Auto Pilot"
"Cycle Nav Points"

and i hope someone can provide me with them .

[AdmiralRalwood]

The "hasXSTR" attribute of those keys (alongside "Top-Down View") is set to false (meaning FSO will never try to translate them). This is, perhaps, less than desirable (let alone intuitive).

[Deepstar]

That is indeed unfortunate. But thanks for the information. So it seems that i am nearly finished with this file. (only needs some textposition changes)

Had this "hasXSTR"=false decision a specific reason?

I mean, if you do not cover that entry in the strings file, it should still show the english text in the game, right?
But it would be translateable with a string if you add it in the file (or use a tbm)?

[AdmiralRalwood]

If I understand how the string indices for key controls work, turning hasXSTR on will cause the string indices for the other controls to get out of alignment. My only familiarity with this code is just what I read looking into this, though, so I'd rather not speculate on why it was done or how to fix it when somebody else probably has much more familiarity with this code.