cloud34221.sbs

How to Localize Apps Quickly with Sisulizer Standard

Written by

admin

in

Installing and Configuring Sisulizer Standard — Step‑by‑Step TutorialSisulizer Standard is a desktop application for software localization that helps developers, translators, and project managers extract text from applications, translate it, and produce localized builds. This tutorial walks through installing Sisulizer Standard, configuring it for a Windows project, preparing resources for translation, working with translation memories and glossaries, and creating localized outputs. Screenshots and exact menu names may vary by version; this guide focuses on typical workflows and best practices.

1. System requirements and preparation

Before installation, make sure your environment meets the basic requirements:

  • Operating system: Windows 10 or later (Sisulizer is Windows-native).
  • Disk space: At least 200 MB for the application plus additional space for projects and backups.
  • Permissions: Administrator rights may be needed for installation or integrating with IDEs.
  • Files to localize: Source application files (EXE/DLL, resource files, XML, XLIFF, RESX, INI, PO, HTML, etc.).
  • Optional: A copy of your source project and a version control backup before making changes.

2. Downloading and installing Sisulizer Standard

  1. Visit the Sisulizer website and navigate to the download page for Sisulizer Standard.
  2. Download the installer package (usually an .exe).
  3. Run the installer as an administrator: right-click the .exe and choose “Run as administrator” if required.
  4. Follow the installation wizard:
    • Accept the license agreement.
    • Choose an installation folder (default is usually fine).
    • Select any optional components (examples, plugins, or integration tools) if prompted.
  5. After installation, launch Sisulizer Standard from the Start menu or desktop shortcut.

3. Creating a new localization project

  1. Open Sisulizer Standard and choose File → New Project (or click the New Project icon).
  2. In the New Project dialog:
    • Enter a project name (e.g., MyApp_Localization).
    • Choose the source language of your application (e.g., English (United States)).
    • Set the target languages you plan to translate into (you can add them now or later).
  3. Choose the project type if prompted (e.g., Windows application, web resources, or a generic project). Sisulizer usually auto-detects resource types when you import files.

4. Importing source files and extracting localizable strings

Sisulizer supports many resource formats. Typical import workflow:

  1. Click Project → Add Files or use the Import wizard.
  2. Select the files to import: EXE/DLLs, .resx, .xml, .po, .html, .js, .ini, etc. For compiled binaries, Sisulizer will attempt to extract embedded resources.
  3. After import, Sisulizer will parse files and list localizable items (strings, menus, dialogs). Review the extracted items for relevance — some strings (IDs, keys, code literals) may be excluded automatically.
  4. You can refine extraction with filters:
    • Exclude files or patterns.
    • Configure which resource types to parse.
    • Use regular expressions to include/exclude specific strings.

Tips:

  • For .NET apps, include both EXE/DLL and satellite assemblies when available.
  • For HTML/JS, ensure encoding is correct (UTF-8/UTF-16 as appropriate).

5. Project structure and navigation

After extraction, the Sisulizer interface typically shows:

  • A project tree with files, dialogs, and resource categories.
  • The translation grid or editor with source text and target translation columns.
  • Context panes showing dialog previews or resource properties.

Familiarize yourself with:

  • The Editor window for translating individual strings.
  • The Grid view for bulk edits and sorting/filtering.
  • The Preview pane to see string context and layout.

6. Using translation memory ™ and glossaries

Sisulizer supports translation memories and glossaries to speed translation and improve consistency.

  • Create or import a TM:
    1. Project → Translation Memory → Create or Import.
    2. Import TMX or other supported TM formats if you have previous translations.
  • Configure TM usage:
    • Set similarity thresholds for fuzzy matches.
    • Choose whether to auto-insert 100% matches.
  • Create a glossary (termbase):
    • Add domain-specific terms and preferred translations.
    • Configure case and plural rules if supported.

Best practices:

  • Populate TM with high-quality translations first.
  • Use glossary for brand names, product-specific terms, and legal phrasing.

7. Translating: manual and assisted workflows

Manual translation:

  • Open each source string in the Editor, enter the target text, and confirm.
  • Use the Preview pane to verify context and UI fit (length constraints, buttons).

Assisted translation:

  • Use TM and automatic insertion of matches to pre-fill translations.
  • Enable machine translation (if available in your Sisulizer edition) for suggestions — review thoroughly.
  • Use Find/Replace, bulk operations, and filters to handle repetitive edits.

Quality checks:

  • Use built-in QA tools: missing translations, length checks, numeric/format checks.
  • Run pseudo-localization (if available) to test UI with longer strings and special characters.

8. Managing encodings and fonts

  • Ensure target files use appropriate encoding (UTF-8/UTF-16) when exporting.
  • If your target language uses characters outside the Latin set, verify font support in your application/UI so text renders correctly.
  • Test localized builds on machines with target locale settings.

9. Exporting localized files and creating builds

Once translations are complete and QA passed:

  1. Choose Project → Export or File → Generate Localized Files.
  2. Select output formats (EXE/DLL, .resx, XML, HTML, etc.) and target languages.
  3. Configure naming and output folders—use separate folders per language (e.g., MyApp r-FR).
  4. For binaries, Sisulizer may generate localized resource DLLs (satellite assemblies) or direct localized executables, depending on your workflow.
  5. Copy localized resources into your application build or use your build system to include generated resources.

Test the final localized build on target systems and languages.

10. Collaboration and versioning

  • Export and share TMX or XLIFF files with translators who use different tools.
  • Use project backups and version control for Sisulizer project files (.sslproj or similar).
  • If multiple translators work concurrently, split by language or module and merge translations via TMX/XLIFF imports.

11. Troubleshooting common issues

  • Missing strings after import: check file filters and re-run extraction with broader settings.
  • Encoding errors (garbled characters): ensure correct source encoding and export encoding.
  • UI truncation: enable pseudo-localization to spot layout problems early; shorten or rephrase strings as needed.
  • Duplicate entries: use cleanup tools and consolidate resources before translation.

12. Useful tips and best practices

  • Start with a clean source: remove obsolete strings and consolidate duplicates.
  • Keep translations in TMX to reuse future projects.
  • Use placeholders consistently (e.g., %1, {0}) and document their order for translators.
  • Regularly back up the Sisulizer project file.
  • Run QA checks early and often.

If you want, I can produce a checklist you can print for your localization team, provide sample configuration settings for .NET or HTML projects, or create step-by-step screenshots tailored to a specific Sisulizer version.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

More posts