Using of SLMake tool – export task

This article is part of article set related to SLMake using. In this article you can find information about export task. This task exports data from the project to a file. Equals to “File” -> “Export” menu of Sisulizer.  Click here, if you would like go to our article with tasks index.

Syntax

SlMake export file project

  • file – A file (.txt, .tmx, .xlf or .xls) to be exported
  • project – Sisulizer project file (.slp).

Possible options are

-format:X – File format of the export file:

  • 0 – Ansi
  • 1 – UTF-8 (Default)
  • 2 – UTF-16, little endian
  • 3 – UTF-16, big endian

-escape:X – String escape method:

  • 0 – No escape characters (Default)
  • 1 – C/C++ escape characters: \n\r…
  • 2 – Sisulizer escape characters: #l#c…

-lang:X – List of language codes to be exported. Separate multiple codes with semicolon. Format is ll[-CC][.src]:

  • ll – Two-character ISO-639 language code (e.g. “en”)
  • CC – An optional two-character ISO-3166 country code (e.g. “US”)
  • src – An optional three-character Sisulizer script code

-status:S – A string that contains the translation statuses that are included. Separate multiple values with semicolon. Possible values are:

  • untranslated – Include translations having Not Translated status
  • best – Include translations having Best guess status
  • auto – Include translations having Auto translated status
  • translated – Include translations having Translated status
  • review – Include translations having For review status
  • complete – Include translations having Complete status

The default value is to include all translation statuses.

-rowstatus:S – A string that contains row statuses that are included. Separate multiple values with semicolon. Possible values are:

  • new – Include rows having New status
  • unused – Include rows having Unused status
  • inuse – Include rows having In use status
  • changed – Include rows having Changed status

The default value is to include all row statuses.

-readonly:S – Specifies how rows having a Read only status are filtered:

  • ignore – Ignore Read only status (Default)
  • yes – Include rows having Read only status
  • no – Exclude rows having Read only status

-invalid:S – Specifies how rows having a Invalidated state are filtered:

  • ignore – Do not use this state when filtering rows (Default)
  • true – Include only rows that have been set Invalidated
  • false – Include only rows that have not been set Invalidated

-marked:S – Specifies how rows having a Marked state are filtered:

  • ignore – Do not use Marked state when filtering rows (Default)
  • true – Include only rows that have been set Marked
  • false – Include only rows that have not been set Marked

-dup:X – Specifies how duplicate strings are filtered:

  • 0 – No filter (Default)
  • 1 – First
  • 2 – Those having different properties

-sort – Sort exported data.

-q – Quiet mode. Only errors are shown.

-w – Result code is 2 if errors, 1 if warnings, and 0 if successful. Otherwise result code is 1 if errors and 0 in other cases.

-e – Show detailed error information.

-h – Show detailed help about a task.

Following options are used when exporting to a TMX file.

-admlang:X – Admin language (en).

-nosingle – Do not use single XML tags (e.g. ).

-srclang:X – Source language (*all*).

-tmxcase:X – Case of the lang-attribute:

  • 0 – Default case, en-US (Default)
  • 1 – Lower case, en-us
  • 2 – Upper case, EN-US

-tmxdtd:X – DOCTYPE and DTD usage:

  • 0 – No DOCTYPE tag (Default)
  • 1 – DOCTYPE tag with local DTD file name
  • 2 – DOCTYPE tag with DTD URL file name

-tmxver:X – TMX version. 1.1 – 2.0. Default value is 1.4.

-tmxitems:S – A string that contains the items that will be written to file. Separate multiple values with semicolon. Possible values are:

  • empty – Writes empty translations
  • comment – Writes comments
  • context – Writes context values
  • status – Writes translation status values
  • rowstatus – Writes row status values
  • maxchars – Writes maximum length in characres values
  • maxpixels – Writes maximum length in pixels values

The default value is to contain none of above.

Following options are used when exporting to a XLIFF file.

-xlfver:X – XLIFF version. 1.0 – 1.2. Default value is 1.2.

-xlfitems:S – A string that contains the items that will be written to file. Separate multiple values with semicolon. Possible values are:

  • noempty – Does not write empty translations
  • comment – Writes comments
  • context – Writes context values
  • status – Writes translation status values
  • rowstatus – Writes row status values
  • maxchars – Writes maximum length in characres values

The default value is to contain none of above.

Following options are used when exporting to a text file.

-separator:X ASCII hex value of the column separator character of text file. Default value is 9 (0x9 = tab).

-addcomment – Adds row comment column as the last column

-addtcomment – Adds translation comment column next to the translation column

-context:X – Position of the context column:

  • 0 – No context column (Default)
  • 1 – Context column is the first column
  • 2 – Context column is the second column after the original column
  • 3 – Context column is the last column

-nobom – No byte order mark (BOM) is written

-quote:X – Quotes that are used:

  • 0 – No quotes (Default)
  • 1 – Single quotes (‘)
  • 2 – Double quotes (“)

Following options are used when exporting to an Excel file.

-addcomment – Adds row comment column as the last column

-addtcomment – Adds translation comment column next to the translation column

-context:X – Position of the context column:

  • 0 – No context column (Default)
  • 1 – Context column is the first column
  • 2 – Context column is the second column after the original column
  • 3 – Context column is the last column

-noheader – Do not write language names as the first row.

Examples

  • SlMake export Translat.txt Sample.slp – Export to a text file from Sample.slp
  • SlMake export Translat.xls -lang:fi;de Sample.slp – Export Finnish and German data to an Excel file from Sample.slp
  • SlMake exchange Translat.tmx -lang:de -status:translated;review;complete Sample.slp – Export complete, reviewed and translated strings of the German column

Janusz

Using of SLMake tool – exchange task

This article is part of article set related to SLMake using. In this article you can find information about exchange task. This task creates an exchange package and equals to “File” -> “Exchange” menu of Sisulizer. Click here, if you would like go to our article with tasks index.

Syntax

SlMake exchange file project

  • file – An exchange file (.sle or .exe) to be created
  • project – Sisulizer project file (.slp).

Possible options are

-lang:X – List of language codes to be exchanged. Separate multiple codes with semicolon. Format is ll[-CC][.src]:

  • ll – Two-character ISO-639 language code (e.g. “en”)
  • CC – An optional two-character ISO-3166 country code (e.g. “US”)
  • src – An optional three-character Sisulizer script code

-status:S – A string that contains the translation statuses that are included. Separate multiple values with semicolon. Possible values are:

  • untranslated – Include translations having Not Translated status
  • best – Include translations having Best guess status
  • auto – Include translations having Auto translated status
  • translated – Include translations having Translated status
  • review – Include translations having For review status
  • complete – Include translations having Complete status

The default value is to include all translation statuses.

-rowstatus:S – A string that contains row statuses that are included. Separate multiple values with semicolon. Possible values are:

  • new – Include rows having New status
  • unused – Include rows having Unused status
  • inuse – Include rows having In use status
  • changed – Include rows having Changed status

The default value is to include all row statuses.

-readonly:S – Specifies how rows having a Read only status are filtered:

  • ignore – Ignore Read only status (Default)
  • yes – Include rows having Read only status
  • no – Exclude rows having Read only status

-invalid:S – Specifies how rows having a Invalidated state are filtered:

  • ignore – Do not use this state when filtering rows (Default)
  • true – Include only rows that have been set Invalidated
  • false – Include only rows that have not been set Invalidated

-marked:S – Specifies how rows having a Marked state are filtered:

  • ignore – Do not use Marked state when filtering rows (Default)
  • true – Include only rows that have been set Marked
  • false – Include only rows that have not been set Marked

-dup:X – Specifies how duplicate strings are filtered:

  • 0 – No filter (Default)
  • 1 – First
  • 2 – Those having different properties

-setup – Create exchange package that installs Free Edition.

-sourcefiles – Exchange the source files (e.g. EXE, XML, HTML) of the project.

-spellcheck – Exchange spell checker files.

-uilangs – Include languages files of Sisulizer.exe.

-name:”S” – S is a string that contains the package name.

-des:”S” – S is a string that contains the package description.

-author:”S” – S is a string that contains the author name.

-pwd:”S” -S is a string that contains the password of the package.

-q – Quiet mode. Only errors are shown.

-w – Result code is 2 if errors, 1 if warnings, and 0 if successful. Otherwise result code is 1 if errors and 0 in other cases.

-e – Show detailed error information.

-h – Show detailed help about a task.

Examples

  • SlMake exchange Trans.sle Sample.slp – Create a package containing all the languages of the project
  • SlMake exchange Trans.sle -lang:de -status:untranslated Sample.slp – Create the German package containing the untranslated items
  • SlMake exchange Trans.sle -sourcefiles Sample.slp – Create a package containing the source files
  • SlMake exchange Trans.exe Sample.slp – Create a package that installs Translator’s Edition

Janusz

Using of SLMake tool – duplicate task

This article is part of article set related to SLMake using. In this article you can find information about duplicate task. This task translates duplicate strings. Click here, if you would like go to our article with tasks index.

Syntax

SlMake duplicate project

  • project – Sisulizer project file (.slp).

Possible options are

-lang:X – List of language codes to be translated. Separate multiple codes with semicolon. Format is ll[-CC][.src]:

  • ll – Two-character ISO-639 language code (e.g. “en”)
  • CC – An optional two-character ISO-3166 country code (e.g. “US”)
  • src – An optional three-character Sisulizer script code

-nosave – Do not save the project file even if it gets changed.

-q – Quiet mode. Only errors are shown.

-w – Result code is 2 if errors, 1 if warnings, and 0 if successful. Otherwise result code is 1 if errors and 0 in other cases.

-e – Show detailed error information.

-h – Show detailed help about a task.

Examples

  • SlMake duplicate Sample.slp – Translate duplicate strings in all columns.
  • SlMake duplicate -lang:de;ja Sample.slp – Translate duplicate in German and Japanese columns.

Janusz

Using of SLMake tool – create task

This article is part of article set related to SLMake using. In this article you can find information about create task. This task build localized file(s). Click here for our article with tasks index.

Syntax

SlMake create <options> project

  • project – Sisulizer project file (.slp).

Possible options are

-lang:X – List of language codes to be created. Separate multiple codes with semicolon. Format is ll[-CC][.src]:

  • ll – Two-character ISO-639 language code (e.g. “en”)
  • CC – An optional two-character ISO-3166 country code (e.g. “US”)
  • src – An optional three-character Sisulizer script code

-include:”S” – S is a string that contains the name of the source(s) that will be built. Separate multiple sources with ; character.

-exclude:”S” – S is a string that contains the name of the source(s) that will not be built. Separate multiple sources with ; character.

-nosave – Do not save the project file even if it gets changed.

-forcesave –  Save the project file even if an error occurs. If no save options is given the project is saved if it gets changed and no error has occured. forcesave overrides nosave.

-config:”S” – S is an Visual Studio configuration. Value is not saved. This is used by .NET sources to select a configuration.

-input:”S” – S is an input directory. Value is not saved.

-output:”S” – S is an output directory. Value is not saved.

-al:”S” – S contains Assembly Linker parameters. Value is not saved. If data contains ” characters encode them with \”. This option applies only for .NET sources.

-q – Quiet mode. Only errors are shown.

-w – Result code is 2 if errors, 1 if warnings, and 0 if successful. Otherwise result code is 1 if errors and 0 in other cases.

-e – Show detailed error information.

-h – Show detailed help about a task.

Examples

  • SlMake create Sample.slp – Create all localized files
  • SlMake create -lang:de;ja Sample.slp – Create German and Japanese localized files

Janusz

Using of SLMake tool – add task

This article is part of article set related to SLMake using. In this article you can find information about add task. This task adds a new source and creates a new project if required. Click here, if you would like go to our article with tasks index.

Syntax

SlMake add file project

  • file – A source file to be added. File name can contain wild cards (* and ?).
  • project – Sisulizer project file (.slp).

Possible options are

-type:X – where X is source type. Below is list of possible source types:

  • net – .NET assembly file (.exe, .dll)
  • nettxt – .NET text resource file (.txt)
  • cb – C++Builder binary file (.exe, .dll, .ocx)
  • delphi – Delphi binary file (.exe, .dll, .ocx)
  • java – Java resource file (.java, .properties
  • source – Source code file (.cpp, .pas, .bas, .java, .pl, etc)
  • txt -Text file (.txt)
  • vb – Visual Basic binary file (.exe, .dll)
  • win – Windows C/C++ binary file (.exe, .dll, .ocx)

If no type is specified SlMake detects the type of the source.

-lang:X – list of language codes that will be in project if it is created. Separate multiple codes with semicolon. Format is ll[-CC][.src]:

  • ll – Two-character ISO-639 language code (e.g. “en”)
  • CC – An optional two-character ISO-3166 country code (e.g. “US”)
  • src – An optional three-character Sisulizer script code

Use script code if the language does not use the default script. Simplified Chinese is “zh” or “zh-CN”, Traditional Chinese is “zh.tra” or “zh-TW”.

-origlang – Language code of the original language of the source.

-outitem:X  – Output files. Possible values are:

  • 0 – Localized files (Default)
  • 1 – Multilingual file
  • 2 – Resource files/DLLs
  • 3 – Embedded resource files

 

-noimport – Do not import translations from existing files.

-subdirs – Localize all similar files in the sub directories as well.

-q – Quiet mode. Only errors are shown.

-w – Result code is 2 if errors, 1 if warnings, and 0 if successful. Otherwise result code is 1 if errors and 0 in other cases.

-e – Show detailed error information.

-h – Show detailed help about a task.

Examples

  • SlMake add Sample.exe Sample.slp – Add Sample.exe source to the project.
  • SlMake add *.txt -type:txt Sample.slp – Add all text files in the current directory to the project.

Janusz

 

Using of SLMake tool – general information

In many cases the developer uses a build file that compiles the release version of the application, creates the setup applications, etc. In such process the interactive Sisulizer application can’t be used. Sisulizer Enterprise edition includes a make tool called SlMake. It is a command line tool and provides an interface for most Sisulizer features including scanning, translation, building, exchanging, importing and exporting. Of course you can use SLMake even if you don’t use it with developer’s tool. Because SLMake is a DOS command tool you can use old, but very useful solution with using batch file. Batch file allows to automate time consuming and often performed operations. You can find this tool in Sisulizer’s installation directory:

c:\Program Files\Sisulizer 4\slmake.exe

Syntax

<Sisulizer’s installation directory path>SlMake <tasks> project [-q] [-w] [-e] [-h]

Below is the list of parameters available for all tasks:

  • -q – Quiet mode. Only errors are shown.
  • -w – Result code is 2 if errors, 1 if warnings, and 0 if successful. Otherwise result code is 1 if errors and 0 in other cases.
  • -e – Show detailed error information.
  • -h – Show detailed help about a task. For example slmake import -h displays help for import task. If you use –h with SLMake without task, that is, slmake –h, it displays general help about SLMake.

Tasks

Below is the list of available tasks. These tasks are described in separated articles. To each task name is assigned a link to appropriated article. So when you click on the name of a task in below list, it redirects you to an article with description for the selected task.

  • add – Add a new source and create a new project if needed
  • create – Create localized items
  • duplicate – Translate duplicate strings
  • exchange – Create an exchange package
  • export – Export data to a file
  • fillpseudo – Fill pseudo translation
  • import – Import data to project
  • remove – Remove unused items
  • removepseudo – Remove pseudo translation
  • report – Create a project report
  • scan – Scan project
  • translate – Translate strings using translation engines
  • validate – Validate original or translated values

If no task is given the create task is performed. project is a Sisulizer project file (.slp) to be processed.

Janusz