Logging: The Import Log

When the Log Import option is checked on the logging tab of the general options window, VBLM logs all import operations. The disk file (VBLM Import Log.txt by default, but you can change this), is written to the same directory as the parent VB project. If the file exists, VBLM handles it per your setting on the logging tab.

The import log begins with the date and time, the project, the table being imported into, and the LMX file:

VBLM Import Log: 20-Mar-02 11:58 AM

VB Project = C:\Program Files\DevStudio\VB\samples\PGuide\Optimize\Optimize.vbp

Language Table = Enumerate

Import File = C:\Program Files\DevStudio\VB\samples\PGuide\Optimize\Pig Latin.lmx

[Begin LMX File Config]

[ExportFile]

Version=6

SourceLanguage=English

TransLanguage=Pig Latin

Format=Pairs

Content=All

Sorted=Yes

Quoted=No

NoAmpersands=No

Spacing=Single

ExclusionInfo=Yes

NumEntries=188

IncludeUserInfo=No

MissingTrans=NoExport

[End LMX File Config]

Then it logs each import, showing the design language string, its context, the translation imported, and any previous translation being replaced:

Replaced "S0010"

English=" Image Controls"

Context=String#2 in [MsgBox "Allocated " & Str$(i) & " Image Controls", vbInformation, "Image Control"]

Imported Pig Latin="Imageay ontrolsCay"

Replaced "S0104"

Any imported string exclusions are also logged:

The following strings were marked as excluded

"Visual Basic 4.0 Optimization Examples",Context=1,[Description = "Visual Basic 4.0 Optimization Examples"]

"Visual Basic 4.0 Optimization Sample Code.",Context=1,[VersionComments = "Visual Basic 4.0 Optimization Sample Code."]

"VBLM Test Constant",Context=1,[Const WW3 = "VBLM Test Constant"]

"VBLM Test Constant",Context=1,[Public Const WW1 = "VBLM Test Constant"]

The log closes with a summary of the import:

Info: The last successful import was from line 768

168 matches found and translations imported

4 strings were marked as excluded.