Localised strings in FM-16

Use cases

• Have reasonable terminology for custom tool bars, custom dialogues and custom scripts.
• Find the correct label of a button for support of a client with other language.
• Find the ESC sequence for a known command in French
• Is there really no tool tip for a particular command? Yes, things like this happen.

Scope

The PDF contains all extracted localised strings from the following dlls: fmdlg.dll, fmres.dll, owlres.dll and the menus and toolbars of the structured interface, WYSIWYG workspace. I assumed that this workspace contains most information.

Table	File	Resources considered	# table rows
Menus	menus.cfg	Labels	2017
Commands	cmds.cfg mathcmds.cfg wincmds.cfg	Command, label, short cut, definition	1013 cmds 267 mathcmds 509 wincmds
Tool bars	*.xml	Command, image base, tool tip	80 - but there are much more without tool tips
Dialogues	fmdlg.dll	Dialog	4630 for 408 dialogues
Messages and list items	fmres.dll	String table	7020
XSTR Glossary	owlres.dll	XSTR - Glossary	421

Comments

I started this project in 2018 - then only with the entries I just needed. The document had about 60 pages. 2022 I took the effort with the help of these tools:

• ResHacker to extract the resources into text files
• AHK scripts (see end of documentation)
• Regular expressions in my favourite editor EidtPad pro

… and we have about 16000 table rows with English, German and French text in a 360 page PDF.

Caveat

Any software from D+DD is provided by the author and contributor "as is" and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed.