This is a supported release.  It fixes several errors in v2.0.1, adds several features, and is even easier to install.

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.

The older single-user version 1.2 branch, which does not require AAD app registration, is still supported, and a new version will be released in the coming days with many of the same new features and bug fixes.
 

New Features

• Parameter ":n" after the language to use a unique name based on the original file name rather than translating the file name.
• Command line parameter "publish" for publishing translations
• In AppReg, check for and install Module SharepointPNPPowershellOnline if it's not installed
• In AppReg, if there is an error when setting permissions, display the message in the browser, otherwise "Success".
• At the end of Appreg, check and add/upgrade the app to tenant app catalog
• Removed Category Id and Region parameter in User Interface. These were often given incorrect values, and usually do not need a value. They are available through the command line.
• Several error messages changed to say why the error occured and what to do differently
• Site-specific configuration section (3 fields) is hidden unless expanded by admin user. By default the app will use the tenant configuration, but it is possible to override it at the site level.
• When loading the app page, automatically check & show app version and server version. If not, provide a link about server installation.
• Pre-populate the source item language if it's already set or detectable.
• Option to use "fr-ca" rather than "fr-fr"
• App is more consistently called "PointFire Translator Add-in"
• Passwords are more consistently hidden on screen
• The web interface has a more intuitive way to enter the name of a file within a folder, as "/foldername/filename"
• For web interface and scripts, checking that username in stored credentials is authorized is moved to Set Credentials rather than re-checking every time.
• Add-in main screen is more aware of different scenarios with MLP or not, with no alternate languages and with some and with all alternate languages, and gives appropriate advice.
• Now supports over 100 languages

Resolved Issues

• Doing Set Credentials while SPSiteURL is the root site gave (403) Forbidden

• Doing set credential under power Automate tab, it is adding unnecessary SPsiteUrl value.

• In certain languages, Home page translations through web interface gives "ERROR: The property or field 'Name' has not been initialized. It has not been requested or the request has not been executed. It may need to be explicitly requested."

• When translating classic calendar, set values for start time and end time field that do not depend on time zone of user or server.

• When translating classic calendar, sometimes get "ERROR: The given list/library is not present in site."

• if translating the home page to 2 or more languages at a time then the translated page is blank for some languages

• Users now need "Edit" permission, not "Manage Lists" to translate with the app. Previously when trying to translate a document with permissions, could get the errors "ERROR: Something went wrong in getList:Access denied.", "ERROR: Abnormal termination (Access denied.)"

• Web interface: when translating a document that does not exist in the document library, it showed Success message on the top right corner while in the bottom it showed File cannot be found in Document library.

• When translating a PDF, got complex error message if Office was not installed on server, like "Retrieving the COM class factory for component with CLSID" or "Class not registered" Replaced with a clearer message.

• While translating a document using the web interface, gave this error "ERROR: User name in stored credentials must match one of the authorized users in Usernames." even though user is authorized.

• Translating with SharePoint Multilingual Page Publishing feature gave the message "You can not translate the page." Replaced with clearer messages saying why not.

• Re-translating with SharePoint Multilingual Page Publishing was not translating new changes.

• Difficulties in translating a page within a folder. Syntax for documents within folders made more flexible.

• Translating site pages with MLP feature for multiple languages, including unsupported ones, it shows the success messages but not the errors.

• While translating to multiple languages through App, the Translation Details is only showing the message "Documents translated successfully: 5". There is no message to which languages the page is translated.

• Some interfaces were not recognizing "zh-CHS" as a SharePoint language and an alias of "zh-CN"

• When translating a list item, the Translation details is blank when translation is successful.

• After translation, language code within the file name was sometimes incorrect for recently-supported languages like Macedonian and unsupported languages Basque and Galician.

• When translating a document inside a folder to multiple languages, Chinese simplified translation did not work. When Chinese simplified and Chinese traditional were both requested, both translations are the same.

• After successful translation send it again for retranslation, in query result it says that it successfully translated for zh-cn and zh-tw (should not re-translate if original is unchanged). Similar issues for (sv,it,et,uk,pl,cs,bs,hr,bg,sk,da,sl,ru,es,de)\

• Translating pages with MLP to all languages, if the page does not have copies for MLP folders in all site languages, it does not show which ones are missing.

• PointFire 365 and MLP both active (not supported), translate library using web interface to pt-pt and pt-br. Query results shows only one translation.

• MLP is active, translate the SitePages using 'Translate SharePoint Library', re-translation of the pages shows successful message, despite nothing to retranslate.

• MLP is active, translate the SitePages without having MLP copies or folders, the message showed only failed but did not say which ones or why.

• Translate through Translate SharePoint library, pages within a folder, then re-translate. it shows success message. (should not re-translate unchanged pages)

• Translate through Translate SharePoint library, pages within a folder. Page title is not always translated inside the page.

• Translate a text file to all language and then wait for some hours then send the same file for re-translation. Sometimes get the error " The remote server returned an error: (401) unauthorized". This may be because the submit button was double-clicked.

• Sent a document for translation to pt-pt,pt-br. File names incorrect, pt-pt document name is Documento9[pt-br].docx, pt-br document name is Documento9[pt-pt].docx if original file name ends with a digit.

• When using App and using MTS. discontinued language code "sr-latn-cs" was still accepted, should map to "sr-Latn-RS", if it is ever used in error.

• In communication site, send a Library for translation to fr,de,es,pt-br using web interface. The document did not translate to pt-br. But if we specify only pt-br then it is translated successfully.

• When we translate a document to Dari (prs or prs-af) it returns with Item Language set to "fa"' in UI.

• When we send a page for translation after making the library multilingual directly through the PointFire Translator app then the item name is showing twice in the message.

• After clicking on the "Go back to site" button too soon, the temporary file was not deleted.

• If it fails because document is locked (open for editing) or other reasons, the temporary file was not deleted.

• In general when the Translator server is not available, the app should switch to the MTS service. In some cases it does not switch, it shows an error message saying it can't reach it.

• When the app is adding the Item Language column, apply to all content types, set the default language and the language of existing items like PF365 does

• In PointFire Translator Add-in app Page, "Go back to site" button is sometimes not working. If we click on this it is redirecting to the same page.

• On a site with MLP, all languages, incorrectly had errors for language codes ga-ie, no, az-latn-az, mk-mk, kk-kz

• Activate all language in PF 365. Then select a document and send it for translation through MTS. Don't select any source language. After translation, is translated to English and there are two documents with the same source item and item language "en".

• The Add-in said "you are about to translate xxxx.docx into all the languages of this site" even in only some languages selected. Now lists the languages instead.

• The Add-in now switches to the MTS in most situations when the PointFire Translator Server is not reachable.

• When we send a document but the document does not exist in the document library. It is showing Success message on the top right corner while in the bottom it is showing that File cannot be found in Document library

• When you enter "txfire setcredentials /?" in the command line, it gives a list of the arguments, but it was not clear which are mandatory.

• When you send a page for translation after making the library multilingual through the PointFire Translator app then the item name is showing twice in the message

• When all languages are activated, and clicked on a calendar item to translate through PointFire translator app, the scroll bar was not appearing on the pop up window.

• Issues with double quotes within mstrans.dic file

• For TranslateDocuments.ps1, while translating a document having a title with space, it is showing cannot be found in library.
• Many other small fixes and performance enhancements

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