Today, we return to our series highlighting Extensions available in ScreenConnect.
One interesting fact about extensions is that they can contain .resx resource files. This means that multiple localizations can be implemented via extensions! In order to faciliatate the production of these resource files, an extension exists. The Translation Extension Builder acts as a helper extension, assisting with the production of new translations for ScreenConnect.
When the Translation Extension Builder is installed, a new option is available at the bottom of the extensions page: "Create Translation Extension". Choosing this new option will start the translation process.
Select the language you wish to translate into, your author name, and the extension's version (this will default to 1.0). Keep in mind, most languages have the option of a generic translation or a specific, regional version; choose your "Culture" option accordingly. Once your initial options are configured, you can choose to create the extension and return later or immediately jump into the resource editor.
The resource editor is formatted in similar fashion to the base resource string tables available within the Appearance menu. For your new translation, just provide the translated equivalents in the righthand boxes. For those with existing translations that have been implemented by placing the files directly on the server, it might also be possible to copy/paste directly into the resource files' XML as well (Note: this will depend on what version your exisiting translation was originally made for).
Translation extensions function by detecting the user's Operating System and Web Broweser language settings. Your users and guests should automatically view their configured language when visiting the web interface for you ScreenConnect installation. Implement any number of translations you want, including those currently in the Online Extension Browser. By using multiple translations, you can ensure that all visitors to your site can view it with their respective language.
Disclaimer: This extension was written by our support team (and in some cases in conjunction with our forum community) in response to customer requests. Extensions are meant to be quick workarounds or immediate solutions to problems. Extensions are not supported under our normal terms of service, as these extensions are outside typical Q/A or development guidelines. Questions for extensions should be addressed in their respective forum posts. Suggestions for improvements (enhancements or defects) should also be queued in the proper post for consideration.