SlMake updates in recent builds

We published on our blog article series about the SlMake tasks in the past. However, our R&D implemented a lot new features in the meantime (Last the article about the Slamke was published in Marth 2010). I always update appropriated articles after changes in SlMake, but it is made without announcements. So, articles are still topical, but our users could overlook it. For this reason I decided write this short preview of all new features implemented to SlMake since March 2010.

Build 343

Added -uilangs parameter to exchange task.

Build 334

Added  -config parameter to create task.

Build 332

Added -origlang and -outitem: parameters to add task

Build 323

Added -subdirs parameter to add task. Here is article about this task.

Build 310

Added -input: parameter to create task.

Build 307

Added -name: parameter to validate task. Here is article about this task.

Build 306

Added -invalid: and –marked: parameters to exchange and export task. Here and here are articles about these tasks.

Build 303

Added -output: and –al: parameters to create task. Here is article about this task.

 

Besides those new parameters our developers improved behavior of some tasks and parameters in the meantime. They also fixed some bugs reported by our users. You can find full info about those changes in our changelog.

If you haven’t read our articles about SlMake yet, I recommend you go to this article with general info and additional links.

Janusz Grzybek

 

Using of SLMake tool – translate task

This article is part of article set related to SLMake using. In this article you can find information about translate task. This task translates project by using translation engine(s). Equals to “Project” -> “Translate Using Translation Engine” menu of Sisulizer.  Click here, if you would like go to our article with tasks index.

Syntax

SlMake translate <options> 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

-engine:S – The name of the translation engine to be used. If empty or “” all engines are used. If no value is given all enabled engines are used.

-first – Use the first translation when two or more translations exists. The default feature is to skip all such translations.

-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 translate Sample.slp – Translate all columns.
  • SlMake translate -lang:de;ja -first Sample.slp – Translate German and Japanese columns. Use first translations.
  • SlMake translate -engine:Google Sample.slp – Translate all columns using Google Translate.

Janusz

Using of SLMake tool – scan task

This article is part of article set related to SLMake using. In this article you can find information about scan task. This task scans the project. Equals to “Project” -> “Scan for changes” menu of Sisulizer.  Click here, if you would like go to our article with tasks index.

Syntax

SlMake scan <options> project

  • project – Sisulizer project file (.slp).

Possible options are

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

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

-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 scan Sample.slp – Scans Sample project file.
  • SlMake scan -q Sample.slp – Scans Sample project file. Writes no output.

Janusz

Using of SLMake tool – validate task

Validate task-name:”S” – Use a named validation list.This article is part of article set related to SLMake using. In this article you can find information about validate task. This task validates a project. Equals to “Validation” menu of Sisulizer.  Click here, if you would like go to our article with tasks index.

Syntax

SlMake validate <options> project

  • project -Sisulizer project file (.slp).

Possible options are

-lang:X – List of language codes to be validated. 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

-original – Validate original values instead translations.

-all – Turn on all default validations.

-default – Turn on the default validations.

-name:”S” – Use a named validation list.

-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 validate Sample.slp – Validate translations.
  • SlMake validate -all -lang:de Sample.slp – Validate German translations using all validations.
  • SlMake validate -original -name:”MyCheck” Sample.slp – Validate original values using MyCheck configuration.

Janusz

Using of SLMake tool – report task

This article is part of article set related to SLMake using. In this article you can find information about report task. This task creates a project report. Equals to “Project” -> “Report” menu of Sisulizer.  Click here, if you would like go to our article with tasks index.

Syntax

SlMake report file <options> project

  • file – A report file (.html) to be create
  • project – Sisulizer project file (.slp).

Possible options are

-items:S – A string that specifies how statistics will be calcalated. Separate multiple values with semicolon. Possible values are:

  • string – Statistics will be calculated in strings
  • word – Statistics will be calculated in words
  • character – Statistics will be calculated in charcters

The default value is to include strings and words.

-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 report MyReport.html Sample.slp – Create a report file.
  • SlMake report MyReport.html -items:string Sample.slp – Create a report file. Show only string statistics.

Janusz

Using of SLMake tool – removepseudo task

This article is part of article set related to SLMake using. In this article you can find information about removepseudo task. This task removes pseudo translation. Equals to “Column” -> “Remove Pseudo Translation” menu of Sisulizer.  Click here, if you would like go to our article with tasks index.

Syntax

SlMake removepseudo <options> project

  • project – Sisulizer project file (.slp).

Possible options are

-lang:X – List of language codes where pseudo translations are removed. 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.

-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 removepseudo -lang:de Sample.slp – Removes pseudo translations from German column.
  • SlMake removepseudo -lang:de;fr Sample.slp – Removes pseudo translations from German and French columns.
  • SlMake removepseudo Sample.slp – Removes pseudo translations from all columns.

Janusz

Using of SLMake tool – remove task

This article is part of article set related to SLMake using. In this article you can find information about remove task. This task removes unused items and save project. Equals to “Project” -> “Remove Unused Items” menu of Sisulizer.  Click here, if you would like go to our article with tasks index.

Syntax

SlMake remove <options> project

  • project – Sisulizer project file (.slp).

Possible options are

-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 remove Sample.slp – Removes unused items from Sample project file.
  • SlMake remove -q Sample.slp Sample.slp – Removes unused items from Sample project file. Writes no output.

Janusz

Using of SLMake tool – import task

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

Syntax

SlMake import file <options> project

  • file – A file (.slp, .txt, or .tmx) to be imported. File name can contain wild cards (* and ?).
  • project – Sisulizer project file (.slp).

Possible options are

-type:X – Source type:

  • 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 to be imported. 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

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

-empty – Import the translation even if it is empty.

-noequal – Do not import the translation if it is same as original value.

-nomatch – Import even if the context and original value do not match. -ignorecase  Ignore character case of imported values.

-ignorewhite – Ignore white spaces of imported values.

-ignorespe – Ignore special characters such as period and hot key (&).

-usepartial – Use partial context.

-overwrite:X – Specifies if current values are overwritten:

  • 0 – Never
  • 1 – If the status is equal or greater than the current one (Default)
  • 2 – If the status is greater than the current one
  • 3 – Always

-status:X – Specifies if the status values are imported:

  • 0 – No
  • 1 – Yes (Default)
  • 2 – Set to the default value

-method:X – Specifies how strings are imported:

  • 0 – By context
  • 1 – By original value
  • 2 – First by context then by original value (Default)

-comment:X – Specifies how comments are imported:

  • 0 – No comments are imported
  • 1 – Comment is imported if the current comment is empty (Default)
  • 2 – Imported comment overwrites the current one

-columns:X – List of text columns. Use this if the imported file is an Excel file. Separate multiple columns with semicolon. Language columns use the same ISO codes as the lang option.The first language column is the original language. Following special columns can be used:

  • co – Context
  • cm – Comment
  • ig – Ignore

-textdef:X – Specifies the name of the text definition that is used. Use this if the imported file is a text file.

-sheet:X – Specifies name of Excel sheet where data is imported from. This is optional and if not given the first sheet is used.

-range:LT:RB – Specifies range of Excel sheet where data is imported from. This is optional and if not given the import range is detected.

  • LT – Specifies the left-top cell (e.g. A1)
  • RB – Specifies the right-bottom cell (e.g. D20)

-escape:X – String escape method:

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

-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 import Translated.slp Sample.slp – Import Translated.slp to Sample.slp
  • SlMake import Translated.slp -lang:de -overwri:3 Sample.slp – Import only the German column. Overwrite the current values
  • SlMake import Sample.txt -textdef:MyFile Sample.slp – Import a text file using MyFile text file definition
  • SlMake import Sample.xls -columns:en;de;ja -sheet:Sheet1 -range:A1:D20 Sample.slp – Import an Excel file containing original (English), German and Japanese columns
  • SlMake import *.xls -columns:co;en;de;ja -lang:ja -method:0 Sample.slp – Import Japanese translations from Excel files containing several columns. Importing is done in a context sensitive way

Janusz

Using of SLMake tool – fillpseudo task

This article is part of article set related to SLMake using. In this article you can find information about fillpseudo task. This task fills pseudo translation. Equals to “Column” -> “Fill Pseudo Translation” menu of Sisulizer. Click here, if you would like go to our article with tasks index.

Syntax

SlMake fillpseudo project

  • project – Sisulizer project file (.slp).

Possible options are

-lang:X – List of language codes to be pseudo 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.

-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 fillpseudo -lang:de Sample.slp – Fills pseudo translation for German column.
  • SlMake fillpseudo -lang:de;fr Sample.slp – Fills pseudo translation for German and French columns.
  • SlMake fillpseudo Sample.slp – Fills pseudo translation for all columns.

Janusz