.tts File

A .tts file is a text file that corresponds to an application. Typically (though not always) the .tts file has the same name as the original ToolBook application with a ".tts" extension. You must have an application's .tts file to translate its sources.

 

The .tts file contains a list of sources, database setup information, global settings, and other information used by the ToolBook Translation System (TTS) Translator.

 

In order to translate an application, you must first specify its .tts file in the Select Sources window.

 

The .tts file entries for a sample application are listed here for reference only.

 

.tts File Entries

 

Explanation

[ODBC]

Provider=MSDASQL

Driver=Microsoft Access Driver (*.mdb)

DriverId=25

Fil=MS Access

ImplicitCommitSync=Yes

MaxBufferSize=512

MaxScanRows=8

PageTimeout=5

SafeTransactions=0

Threads=3

DatabaseTerm=DBQ

 

The [ODBC] section holds information used in connecting to the Access databases.

[CatalogObjectsSkipped]

item1=Popup Page Index

item2=Automatic Menu

item3=Auto Update Web Field

item4=Reusable Graphic

item5=Web Graphic

item6=Feedback Field

item7=Score Field

The [CatalogObjectsSkipped] excludes the objects by ASYM_Wid_Name. This prevents these objects and their individual field, button, and other objects from being included in TTS. This is typically because their functionality is generated automatically and they just cause confusion being included in TTS.

 

[sources]

source1=English

source2=Spanish

 

The [sources] section lists the sources defined for the application.

[current]

ttsSource=English

 

The [current] section shows which source is currently active.

[ToolBook Translation System]

globalContentSetting=rtfContent

useContentGraphics=true

restoreBoundsAndFont=false

writeStringArray=true

storeTooltips=true

 

The [ToolBook Translation System] section stores global settings.

[source English]

db=tts_chocchipSample_english.mdb

 

[source Spanish]

db=\tts_chocchipSample_spanish.mdb

 

There is a [source <sourceName>] section for each defined source. Each such section stores the corresponding database location, and passwords and user names (encrypted) if applicable.