Mechanical engineering companies use Sisulizer to create localized versions of the software that drives their hardware products. Mechanical engineering software is used worldwide to control machines and monitor processes. While many mechanical engineering companies sell their products worldwide, the machine operators typically read and speak only one language. So the translation and localization of the software has to be accurate.
Sisulizer lets mechanical engineers create professionally translated and localized versions available in every language in which the organization does business. In addition to maintaining consistent practices and instructions throughout the world, the software may have to be revised to reflect local laws, safety regulations , and business practices.
Sisulizer lets hardware manufacturers manage these software translation and localization processes efficiently and effectively.
Each localization project within the mechanical engineering company is a three-step process.
First, mechanical manufacturer's IT department uses Sisulizer to scan the software application and locate all of the text. Sisulizer runs on Windows, and works directly with popular development platforms like .Net, C++Builder, Delphi, FireMonkey, Visual Basic, Visual C++, Java, Windows binary files, and other.
The program works visually with HTML and XML. Sisulizer can also grab text from files widely used to store translatable content like .txt, .ini, or .po, JSON files and databases.
The mechanical manufacturing company's software developers determine which Windows resources to translate and localize, including icons, menus, dialog boxes, strings, accelerators, versions, and manifest resources.
The company's IT managers like Sisulizer because it also operates in the mobile world. The software supports Android, and J2ME, .NET for Smart Devices, and Windows Mobile.
Second, translators use Sisulizer's visual editor to do the translation work. The mechanical engineering company's in-house employees can begin the translation work, and mark each phrase as translated properly, auto-translated, translated by best guess, out for review, or complete. Alternatively, the mechanical manufacturer's IT staff can use Sisulizer's Exchange Wizard to create and send an outside translator a single file that contains a self-installing Sisulizer Free Edition, along with the project file.
When the company's translator has completed their translation work, they'll run Sisulizer's Exchange Wizard to create a single file that is sent back to the mechanical manufacturing firm. The translator never has access to your source code, so there is never a risk that you will lose control of confidential information, such as hardware trade secrets. And there is no risk that the translator will accidentally change the source code and adversely affect the operation - or the safety features - of the automation equipment.
The translator never has access to your source code, so there is never a risk that you will lose control of confidential information such as hardware trade secrets. And there is no risk that the translator will accidentally change the source code and adversely affect the operation of the device.
Third, the mechanical company's IT department will build the new localized version of the software. Simply run Sisulizer using the translated file, and build the new version of the software application in the new language. There's no need for the mechanical manufacturer's IT staff to manually track where each text snippet belongs. Sisulizer manages the localization project, and automatically builds the new version of the application that controls your mechanical hardware device.
Sisulizer Tracks the mechanical Company's Text. In support of manufacturing companies, Sisulizer easily handles all languages, including right-to-left and double-byte languages. The program keeps track of what has already been translated, making it fast and inexpensive for you to translate later versions of your software application whenever the company needs to release an updated version of the software, either to support a new version of the hardware or to support a custom version of the hardware