This is a supported release.  It fixes several errors in v2.1.0, and adds several features.

It makes it simple to translate Modern pages such as the ones in Communication and Teams sites and those produced by the Multilingual Page Publishing feature, as well as classic pages, documents, lists, and metadata.  It has several interfaces, including via a SharePoint App, a web interface, scripting, and Power Automate.

IMPORTANT NOTICE

In this release, all of our PowerShell scripts are switching from the legacy SharePointPnPPowerShellOnline module, which stopped being maintained over a year ago, to the new PnP.PowerShell module.  This may require global admin consent.

New Features

• On install, clean up old version's folders, delete old Windows Service from a different directory, but keep some of the settings
• On uninstall, check if any console window is running, stop it if required
• PointFireTranslatorInstaller.ps1 will update the Add-in in the app catalog and in all sites where it is installed. Executed during installation, but can also be run separately
• Removed the code of adding Add-in to the app catalog in AppReg.ps1 since it is now done by the installer script.
• Support the language codes Inuktitut (Latin) - "iu-latn", Somali - "so", Zulu - "zu", and Upper Sorbian - "hsb".
• Change from unsupported SharePointPnPPowerShellOnline module to the PnP.PowerShell module in the scripts 'PointFireTranslatorInstaller.ps1' 'AppReg.ps1'

Resolved Issues

• In web interface, while doing setcredential for the PointFire Translator Add-in, it showed a blank page.
• Says it's translating but not translating some pages on some sites depending on configuration.
• Changed the download location when Microsoft Identity Extensions is not installed.
• Error: "The property or field has not been initialized. It has not been requested or the request has not been executed" This error is sometimes related to the check out policy of the library. With a modern page and with a classic webpart page the content were not getting translated, only the title
• When "required check out" is enabled, some pages did not translate and showed the error "The file "{filename}" is not checked out. You must first check out this document before making changes."
• The AppReg script did not allow hyphens in the host name in the URL.
• In publishing site the Enterprise wiki page contents was not getting translated or partly translated.
• On a classic Enterprise wiki site with an Enterprise wiki home page CEWP was not translating.
• For classic pages, translate "Publishing html" columns, including for custom layouts and custom master pages
• When translating a page which is already translated, it shows the error messages "The property or field has not been initialized. It has not been requested or the request has not been executed. It may need to be explicitly requested.", "The 'sId' argument is invalid.", "Documents failed to translate."
• Classic webparts page not translating content editor and script editor webparts
• When the translation copy is available for a webpart page and we modify the source page and send it for translation then it shows a failed message that the translation is already available.
• Translator server, stored credentials requiring MFA: if access token is expired then refresh the authentication token, but not if running in service mode.
• The "Publish" parameter is no longer case sensitive
• For classic pages with the value Publish=Yes, it is showing the errors "You cannot perform this action on a checked out document." "Documents failed to translate."
• PowerShell sample scripts: Added changes for the Publish parameter.
• While translating a classic page, it is showing ERROR: Version conflict.
• When retranslating the source page, it created another copy for some languages
• Error when a parent site name is a substring of a subsite name
• For the root communication site if we do not enter the "/" after the site url, getting the error "The remote server returned an error: (403) Forbidden. Something went wrong in getAuthorizedContext: The remote server returned an error: (403) Forbidden"
• After translating a modern page, the news webpart filter property language is not always set to the correct value.
• Improvement to the translation of filtering conditions in webparts for certain languages
• For wiki page, success/failure message is not showing properly after translating the page through the Add-in.
• Check if PointFire Translator server is running in console when updating software CheckForTXServiceConsole.ps1
• Check if the service is installed and running when updating sofware
• Various performance improvements in translation.
• While translating modern pages using the Add-in or Translate document option, the page title was not translated like the file name
• Changed upload to the app catalog so that it works when the app catalog site is not English

PointFire Translator can translate individual items or entire libraries or lists in SharePoint Online.  It includes the PoinFire Translator App which will use PointFire Translator Server as a default translation service, and fall back to SharePoint's Machine Translation Service if PointFire Translator is not available.

It can be downloaded here (login required)

http://community.icefire.ca/index.php?/Knowledgebase/Article/View/146/30/pointfire-translator-server

For more information, contact sales@icefire.ca