Live Chat Here!
PointFire Power Translator – v2.0.0.0 beta
Posted by Martin Laplante on 20 December 2019 04:36 PM

This is an unsupported beta release. Thank you for testing it. Please provide feedback to


This version of PointFire Power Translator includes a command-line tool a web interface, and an app interface. After it is installed on a shared server using the "single sign on" procedure, the PointFire Translator app, also v2.0.0.0 beta, supports connecting to this server and translating using the user's own credential. It can also be backward-compatible with installation of the server on the local workstation like previous versions of Power Translator.
The PointFire Translator appp will connect to the PointFire Power Translator service at the URL for which it has been configured, if it is running, but if it is absent it will fall back to using the SharePoint Online Machine Translation Service. PointFire Power Translator works with SharePoint Online (SPO), with OneDrive, and with SharePoint 2019.

The installer will give you the option to start PointFire Power Translator either in console mode, or to install it as a Windows service which can be always on. It will then open the browser interface on the local machine so that you can enter license keys and API keys, and optionally set credentials that it will store. In most cases, these credentials only need to be entered once, even if you are prompted for them later on.

If you install it as a Windows service, then we recommend that you open services.msc, find the PointFire Power Translator service, right-click to select Properties, then under the Log On tab, make sure that Allow service to interact with desktop is checked. Also, in Microsoft Word, click File > Options > Advanced under the "General" heading, and please make sure that "Confirm file format conversion on open" option is disabled.

You need to get a Translator Text API key from Azure

The installation will prompt you for the following information:
⦁ PointFire Power Translator license key. For a trial key, enter "30-day-trial", or contact
⦁ Translator Text API key, see above
⦁ an optional Category ID if you use a specialized translation engine

If you do not choose Single Sign on, you can use stored credentials, in which case it may also require:
⦁ SPO Username, which will be stored for later commands (not required for MFA)
⦁ SPO Password, which will be stored for later commands (not required for MFA)
⦁ SPO site URL, which will be stored as a default for later commands

You may skip these prompts, but you will have to issue the SetCredentials command later. If you are using Multi-Factor Authentication, then the Username and Password may not be required, however a dialog box will open to let you log in, and a new login may be required in later sessions.

PointFire Power Translator can be used from the command line using the TXFIRE exe, or from PowerShell, using scripts like the sample scripts that are provided. However it is easier to use it from PointFire Translator, and app that runs on SharePoint. More details are here

To install PointFire Translator, drag and drop the file to your app catalog and add it to your site, the carry out the configuration steps described in the Power Translator Installation Manual.

New Features

  • Use OAuth2 with single sign on to translate using user credentials
  • Updated installation, including script files ReservePorts.ps1 and SelfSignedCertificate.ps1
  • App configures Azure app parameters and Power Translator server address, with sufficient rights
  • Connect to Power Translator on non-localhost, except for certain operations
  • Add version number to API
  • Credentials don't need locally stored credentials, but still available for standalone use
  • If single sign on is selected, userid, password, and URL not required.
  • Sensitive parameters stored encrypted
  • Power Translator has list of licensed users, denies access to others, authenticated or not
  • If single sign on is checked, show "APIKey" and "Usernames" input boxes. Usernames can be a comma-separate list of user names.
  • Configure API licenses on per-user or per-group basis
  • Licensed user list can use single-domain wildcard (with appropriate license)
  • Overwrite the original with the translation when the target language is of the type fr:o. This should work with new SharePoint multilingual pages and with Variations.
  • Checks for old app/new service and new app/old service combinations
  • Also allow APIKey field that contains a JSON object.
  • support a domain wildcard for the APIkey parameter.
  • More logging of key events
  • Adjust Office registry settings to prevent popup dialogs
  • Better support for root site collection
  • Better support for non-standard domains and SharePoint 2019


The following SharePoint languages are not handled:
⦁ Irish
⦁ Basque
⦁ Azerbaijani
⦁ Galician
⦁ Macedonian
⦁ Kazakh


 pfpowertranslatorsetup.exe (6.57 MB)
 power translator v2 beta.pdf (1.66 MB)
 readme.rtf (6.68 KB)
(0 vote(s))
This article was helpful
This article was not helpful

Comments (0)
IceFire Home | Support Center | PointFire Home
© Copyright IceFire Studios Corp. 2019 - All Rights Reserved.