Die Angebote richten sich an kommerzielle und industrielle Kunden.
Alle Preisangaben sind netto.
Komplette Preisliste.
Suchen Sie die richtige Edition? Besuchen Sie unsere Vergleichstabelle
Sisulizer Version 4 ist ein kostenpflichtiges Update für alle Sisulizer Kunden.
Verwenden Sie noch Sisulizer 3.x, Sisulizer 2008/2010 oder Sisulizer 1.x?
Aktualisieren Sie jetzt auf Version 4 und nutzen Sie alle Neuigkeiten in Version 4.
Version 4 Build 374 veröffentlicht
30.11.2018
Der neue Build kommt mit vielen neuen Features. [mehr]
Tutorials
5.3.2019
Tutorials erneuert [...]
.NET Support erweitert
14.6.2018
Neu im März 2018: [...]
Sisulizer 4 Build 366
1.3.2017
Build 366 - bereit für Visual Studio 2017 [...]
10 Jahre Sisulizer
5.8.2016
Jetzt feiern und sparen [...]
um internationalen Kunden Software in ihrer Sprache anzubieten
um Inhouse-Softwarelösungen zu übersetzen
um mehrsprachige Anwendungen für Firmenkunden zu erstellen
als Lokalisierungs-Dienstleister, um Kundensoftware zu übersetzen
um Software für Behörden zu lokalisieren
um Schulungssoftware an Universitäten zu übersetzen
um Benutzeroberflächen elektronischer Geräte zu lokalisieren
um Software im Medizinbereich zu übersetzen
um Software für Bergbauunternehmen zu lokalisieren
um mehrsprachige Steuerungssoftware im Maschinenbau zu erstellen
Use this sheet to specify how and what part of the project data is exported to the export file.
Specifies what part of project is exported. Possible options are:
Value | Description |
---|---|
Whole project | Exports all items in the project. |
Current node | Exports items from the selected node in the project tree. |
Current view | Exports items from current project view. |
This group lets you include and exclude items based on their translation status. Strings having a status belonging to those statuses that have been checked will be exported to the file. All other will not be exported.
Status | Description |
---|---|
Not translated | Include those items that has Not translated status. |
Best guess | Include those items that has Best guess status. |
Auto translated | Include those items that has Auto translated status. |
Translated | Include those items that has Translated status. |
For review | Include those items that has For review status. |
Complete | Include those items that has Complete status. |
This group lets you include and exclude items based on their row status. Strings having a row status belonging to those statuses that have been checked will be exported to the file. All other will not be exported.
Status | Description |
---|---|
New | Include those rows that has New status. |
Unused | Include those rows that has Unused status. |
In use | Include those rows that has In use status. |
Changed | Include those rows that has Changed status. |
This group lets you include and exclude items based on their data types. Check those data types that you want to export.
This group lets you include and exclude items based on other properties.
You can filter items based on their Do not translate state. Possible values are:
Status | Description |
---|---|
No filter | Do not use Do not tranlate state when filtering rows. |
True | Include only those rows that have been marked Do not translate. |
False | Include only those rows that have not been marked Do not translate. |
You can filter items based on their Invalidated state. Possible values are:
Status | Description |
---|---|
No filter | Do not use Invalidated state when filtering rows. |
True | Include only those rows that have been marked Invalidated. |
False | Include only those rows that have not been marked Invalidated. |
You can filter items based on their Marked state. Possible values are:
Status | Description |
---|---|
No filter | Do not use Marked state when filtering rows. |
True | Include only those rows that have been marked Marked. |
False | Include only those rows that have not been marked Marked. |
Check Row comments if you want to include only those rows that have Row comment.
Check Translation comments if you want to include only those rows that has at least one translation comment.
Specifies if duplicated strings are exported. Possible options are:
Values | Description |
---|---|
No filter | Do not use duplicate state when filtering rows. |
Only first instance | Export only the first instance of each duplicated strings. This means that first string of each duplicate group is exported. All other strings in the same group will be skipped. |
All instances that has different properties | Export those duplicated strings whose properties differs from the other duplicate strings. For example they might have different comment or maximum length. |
Select those languages that you want to be included to the exported file.
By default each item in the language list correspond to the language of the project. For example if you have English, German and Japanese in the project the language list contains these items. When exporting to TMX Sisulizer writes the language codes to the TMX file. Normally it is all right to use the language codes matching to the project languages. In our example it would be
<tuv xml:lang="en"> <seg>Hello</seg> </tuv>
Unfortunately some tools can not cope that well with country netural language codes (e.g. "en" vs. "en-US"). If the other tool that you use requires country part you can change the language code to be used by right clicking the Language list box and choosing Edit. The dialog lets you to define a language that is used when writing tuv elements of the TMX file. For example if you select English in our sample, right click and change the language to English (United States), Sisulizer will write your previous tuv element as
<tuv xml:lang="en-US"> <seg>Hello</seg> </tuv>
Specifies the escape method how line feed, carriage return and other special characters are encoded.
If checked the exported data is sorted by original string value.
If checked the alternative orginal values are used instead of actual original values whne exporting data. This is enabled only if you have set alternative original.