The localization of strings.tbl and tstrings.tbl is a bit tricky. You should be using TBM's, but you have to header all the other languages first, followed by the additional language. You also have to use the same explicit string ID #'s for the portion you want to replace with a translated version.
#English
;
; The control config action text goes between 507 and 619.
;
303, "Protect My Target"
304, "Ignore My Target"
305, "Form on My Wing"
306, "Cover Me"
309, "Rearm Me"
517, "Turn Off Targeting"
521, "Turn Off Targeting of Subsystems"
548, "Attack The Targeted Subsystem"
555, "Return to Base"
583, "Equalize Shields"
592, "Show Nav Map"
599, "Target Newest Ship in Area"
608, "(Multiplayer) Observer Zoom to Target"
609, "Increase Time Compression"
610, "Decrease Time Compression"
611, "Toggle High HUD Contrast"
612, "(Multiplayer) Toggle Network Info"
613, "(Multiplayer) Self Destruct";
#end
#German
#end
#French
#end
#Polish
#end
The above is taken from the MediaVPs mv_strings-lcl.tbm. Note that, while we haven't (yet) changed anything in any of the other languages, they will still display the translated original default entries, but all of the other languages MUST be listed. So, for alkatron to add another language, would need to start with:
#English
#end
#German
#end
#French
#end
#Polish
#end
#YOURLANGUAGEHERE
### Some Translation
### Some Translation
### Some Translation
### Some Translation
#end
As for TStrings, i don't know off the top of my head if there is a way to use a Modular Table for that, but my guess is you would need to header it the same way you would the -lcl.tbm file.