Yes, Sisulizer can save new spell checker entries to custom dictionaries. Custom dictionary entries can be saved directly to Sisulizer project file (file with SLP extension) or as standalone plain text file (file with SLD extension). Both methods have some merits and faults, so selecting of best method depends on your needs.
- Save dictionary to a standalone file is useful, if you want use one custom dictionary file for all your projects, because it gives you one centralized custom dictionary on your PC for all your projects, but this is not good solution, if you would like move your project to other computer or send project to translators. Sisulizer creates separated custom dictionary files for every language after adding new words to custom dictionary. Because SLD files are plain text files, you can share it between other applications.
- Save dictionary to the project file saves custom dictionary entries for all languages to your project file. So you can use all custom dictionaries on all PCs, where you (or your translator) opens the project and you don’t need any additional files using this feature. Sisulizer saves custom dictionaries also to exchange packages. This is the recommended way to save custom dictionary.
Custom dictionary setting on general level
You can change custom dictionaries location via “Tools” menu -> “General” -> “Spelling & Grammar” tab -> “Default custom dictionary location. This is a global setting and all new projects will use this setting for all translation languages. However, this setting doesn’t influence custom dictionary settings of existing projects.
Custom dictionary setting on project level
You can change at any time project’s custom dictionary settings regardless of general settings of custom dictionary. Use right click on translation language column’s header, select “Language properties” from context menu and go to “Spelling” tab. Next, select preferred method from “Custom dictionary location” dropdown menu. This setting is applied only to selected language of specified project, while all new projects use still custom dictionary setting from “Spelling & Grammar” tab of “General Settings”. Of course, for other translation languages of this same project you can use different settings, but I don’t recommend it, because this solution can make a mess in your project.Â Of course, when you change custom dictionary settings on project level, you need to save the project for applying changes. This operation moves all existed entries of custom dictionary to new location.
Custom dictionary setting on source level (for original language)
Sisulizer also supports spell checking for original language. Of course, you can change custom dictionary location (on source level) also for original language. This setting is available via “Spelling” tab of source properties. You can open source properties via “Project” menu -> “Edit source” -> select your source, or via right click on your source node in Project tree -> “Properties” item from context menu.Â This tab looks identical as similar tab for translation languages described above.
Custom dictionary editor
Sisulizer has also implemented a simple editor of custom dictionary entries, where you can manually add new words, edit and remove existing words. You can edit saved entries both to standalone dictionary file and to project. Editor is available via “Column” menu -> “Edit Custom Dictionary…”
This editor supports from build 290 an export & import feature. This feature allows you to transfer custom dictionary entries between projects with custom dictionaries saved in projects, send custom dictionaries to other persons (e.g. for verification) without sending whole project, import dictionary resources from external sources etc…
Sisulizer supports export/import in following formats:
- Sisulizerâ€™s XML files (.sli extension)
- ANSI text files (.txt extension)
- UTF-8 text files (.txt extension)
- Unicode little endian text files (.txt extension)
- Unicode big endian text files (.txt extension)