IMultiFileConverter GetConverterToDefaultBilingual(
	string[] nativeFilePaths,
	string bilingualOutputFilePath,
	CultureInfo sourceLanguage,
	Codepage suggestedCodepage,
	EventHandler<MessageEventArgs> messageHandler
)

Function GetConverterToDefaultBilingual ( 
	nativeFilePaths As String(),
	bilingualOutputFilePath As String,
	sourceLanguage As CultureInfo,
	suggestedCodepage As Codepage,
	messageHandler As EventHandler(Of MessageEventArgs)
) As IMultiFileConverter

IMultiFileConverter^ GetConverterToDefaultBilingual(
	array<String^>^ nativeFilePaths, 
	String^ bilingualOutputFilePath, 
	CultureInfo^ sourceLanguage, 
	Codepage^ suggestedCodepage, 
	EventHandler<MessageEventArgs^>^ messageHandler
)

abstract GetConverterToDefaultBilingual : 
        nativeFilePaths : string[] * 
        bilingualOutputFilePath : string * 
        sourceLanguage : CultureInfo * 
        suggestedCodepage : Codepage * 
        messageHandler : EventHandler<MessageEventArgs> -> IMultiFileConverter 

Parameters

nativeFilePaths

Type: SystemString
The native files to be converted.

bilingualOutputFilePath

Type: SystemString
Full path to the bilingual file to be created.

sourceLanguage

Type: System.GlobalizationCultureInfo
Expected source language of the files.

The same source (and target) language must be used for all the files processed with a single converter instance.

If the language can be determined automatically from the content of the file (e.g. when reading a bilingual format such as TTX), this parameter may be ignored by the parser. If this parameter is left undefined, it is up to the file sniffer and/or parser to try to determine the language. Parser components may report an error or a warning if they cannot reliably identify the language.

suggestedCodepage

Type: Sdl.Core.GlobalizationCodepage
A rough guess of what encoding the files use. This is normally set to the default codepage for the language, but can also be null. This serves only as a hint. A file sniffer can be used to determine the actual encoding for each file. An undefined codepage object can be used if no encoding can be guessed. It is then up to the file sniffer and/or parser to best determine the encoding and report an error if they fail, or a warning if the result is not definite.

messageHandler

Type: SystemEventHandlerMessageEventArgs
An (optional) message handler implementation that will receive any messages reported from file sniffers invoked in the process. If a converter is returned, this message handler will also have been connected to the Message event on the converter. You may specify null for this parameter.

Return Value

Reference