This is a supported release. Thank you to those who tested the beta. Please provide feedback to firstname.lastname@example.org
Please see the installation and configuration manual for details.
This version of PointFire Translator includes a command-line tool, a web interface, and an app interface, and now adds a Power Automate interface. After it is installed on a shared server using the "single sign on" procedure, the PointFire Translator app, also v2.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 PointFire Translator.
The PointFire Translator appp will connect to the PointFire 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 Translator works with SharePoint Online (SPO), with OneDrive, and with SharePoint 2019. Beta 2 adds to this the ability to trigger a translation from a Power Automate flow, with some additional configuration.
The installer will give you the option to start PointFire Translator either in console mode, or to install it a
s 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 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 Translator license key. For a trial key, enter "30-day-trial", or contact email@example.com
⦁ 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 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 http://pointfire.com/products/add-ins/TranslatorManual.aspx
To install PointFire Translator, drag and drop the file PFT-Addin.app to your app catalog and add it to your site, the carry out the configuration steps described in the Translator Installation Manual.
⦁ AppReg.ps1 script to automate Azure Application Registration
⦁ Creation of Custom Connector for Power Automate
⦁ PointFire Power Translator is now called PointFire Translator Server. The app is now called PointFire Translator App.
⦁ Improved web interface, nicer and easier to use, separate scrollable areas for the results.
⦁ Web interface is no longer accessible remotely
⦁ Support for Power Automate via new http interface
⦁ Irish, Kazakh, European Portuguese and Brazilian Portuguese as separate languages
⦁ Māori, Marathi, Gujarati, Punjabi, Malayalam, Kannada, Assamese, Northern Kurdish, Central Kurdish, Dari, Pashto, Odia, French (Canada) non-SharePoint languages
⦁ Fixed 2 versions of Klingon: Klingon (Latin script) and Klingon (pIqaD script)
⦁ Supporting Multilingual Pages feature: when translating a page in a page library, or a set of pages that match a wildcard, overwrite the page if it is an untranslated copy
⦁ Supporting Multilingual Pages feature: translate original page title without the additional text for translators
⦁ Supporting Multilingual Pages feature: do not re-translate if the source item changes, unless the translated document is more recent than the current translation
⦁ Added changes to handle the documents parameter in translatedocument to include the folder structure.
⦁ Translate folder name in a wildcard pattern
⦁ ":o" parameter in the language to overwrite a document with its translation
⦁ ":n" parameter in the language to use original document file name with a suffix rather than translating the document file name.
⦁ If News webpart has Item Language filter, translate the filter condition
⦁ Licensing: check that the username is one of the allowed usernames whatever the method of authentication.
⦁ App feature: Select multiple documents or items
⦁ App feature: Select subset of target languages
⦁ Scripts to generate and install self-signed certificates for testing
⦁ Alternate API regional endpoints. Not extensively tested. Contact us for details.
⦁ Fixes for the broken webpart issue in translated pages that contain certain character sequences
⦁ Translate .rtf files.
⦁ Error: object reference not set to an instance of an object
⦁ Error where upon re-translation of a modified document, document title has changed and the new translation does not overwrite the previous one.
⦁ Updating the version of Translator Windows Service while the service is running
⦁ Integrated the changes from version 1.2.2, including
⦁ Webpart "error has occured"
⦁ Webpart missing on translation to some languages
⦁ Some instances of blank page elements
⦁ Retry after partial translation
⦁ Handle API throttling, other errors
⦁ Translated text misaligned
⦁ Error loading list items
⦁ Issues with custom content types
⦁ Error with quotation marks and unmatched quotation marks
⦁ Make sure the "Documents translated successfully:" message is correct. Sometimes it says 0 and is wrong, and sometimes it says 1 and is wrong
⦁ Blank page issue while translating a page with escaped regex string.
⦁ UTF-8 encoding of console, correcting a lot of “???” for other scripts
⦁ Updated newtonsoft version for various fixes
⦁ Determine whether page file name should be translated
⦁ issue with translation of classic pages.
⦁ Parameter names and some parameter values were case-sensitive in Web Interface
⦁ Issue for several usernames using the same APIKey
⦁ Security: some remote access with incorrect or missing parameters responded with error information but it should avoid volunteering information to unauthenticated users
⦁ Better support for SharePoint 2019
⦁ Better error recovery when translating long Multilingual Translations list
⦁ Correct errors with translating Dari language, Farsi and Dari engines are now separate
⦁ Many performance, error reporting, and potential security issues addressed.
- 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 PointFire Translator server address, with sufficient rights
- Connect to PointFire 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
- PointFire 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:
One of the old Serbian language codes, discontinued by SharePoint, is no longer working. We are working on a fix for those that used it.
Internet Explorer is not supported for the Web interface. Please use Edge or Chrome.