This release corrects certain issues.  If you received an interim release from IceFire support for testing, it must be updated with this release.  This release is a bug fix release, with minor functionality changes.  It is recommended that you update if you have encountered the issues that are discussed.

Documentation is available here.  

The next update release is expected in July 2021.

Release Notes – January 14, 2021

Deploying PointFire 2016

It is recommended that you run the installation on the server where Central Administration is located. Once PointFire 2016 is installed on the target server you can deploy the feature by running the PFConfiguration tool:

Start ->PointFire 2016 ->PFConfig

Note: If you experience issues running the configuration tool from the shortcut, you can navigate to the PointFire directory and run PFConfig or one of the installation scripts directly.

C:\Program Files\IceFire\PointFire2016

⦁ PFConfig.exe – PointFire Deployment Manager
⦁ InstallPointFire.ps1 - to install PointFire using PowerShell.
⦁ UpgradePointFire.ps1 - Upgrade PointFire using PowerShell.
⦁ RemovePointFire.ps1 - To retract the solution using PowerShell

Note: Deploying using the scripts requires additional configuration steps. Please see the install guide for detailed information.

Updating PointFire 2016 

If you are updating an existing PointFire 2016 deployment, launch the PointFire Deployment Manager and follow through the upgrade process, or retract then re-deploy PointFire, or navigate to the installation directory to run the upgrade script.
Note: If configuration keys in the web.config files have been edited manually after PFConfig initially set them, using PFConfig to update the PointFire may erase or overwrite some of those keys. For safety, note the values of the keys currently in web.config prior to updating.

Upgrading from PointFire 2013

If you are upgrading from a PointFire 2013 deployment, please consult the PointFire 2013 v1.0 to 2016 v1.0 Upgrade Guide.

New Features

• none

Resolved Issues

• Values in the Display form of a list do not translate

• No translation in the People Picker dialog box

• The title of the People Picker dialog box (usually "Select People" in English) is not translated

• The term "Active Directory" is not translated in the People Picker dialog box

• In search drop down at the top right of a page, the term "Everything" does not translate

• Values in the "View All Properties" page of a document set do not translate

• Performance issue on Document Set page, from too many calls to PFAPI.aspx

   

Documentation
Documentation for PointFire 2016 is available to be downloaded from the following links:

PointFire 2016 Installation Guide: 
http://community.icefire.ca/index.php?/Knowledgebase/Article/View/134/0/pointfire-2016-documentation

PointFire 2016 Administrators Guide:

http://community.icefire.ca/index.php?/Knowledgebase/Article/View/134/0/pointfire-2016-documentation

PointFire 2016 Users Guide: 

http://community.icefire.ca/index.php?/Knowledgebase/Article/View/134/0/pointfire-2016-documentation

PointFire 2013 v1.0 to 2016 v1.0 Upgrade Guide: 

http://community.icefire.ca/index.php?/Knowledgebase/Article/View/134/0/pointfire-2016-documentation

Support
We recommend that you, or whoever you designate for support, register an account on the support site http://community.icefire.ca/index.php?/Base/UserRegistration/Register . Support can be obtained by clicking on New Ticket on the site after you login or by sending an e-mail to icefire@wssplus.ca

For those who have been using PointFire Power Translator v1.2 or above and have reasons why they cannot upgrade to PointFire Translator v2.0, then PointFire Power Translator v1.2.2.0 is the latest release.

It adds certain features and bug fixes that are already available in v2.0, without the major changes to architecture that v2.0 requires.  Contact sales or support to see which version you should be using.

It can be downloaded here: http://community.icefire.ca/index.php?/Knowledgebase/Article/View/141/12/pointfire-power-translator-v12

Although it is not a PointFire issue, we wish to inform users of SharePoint 2019 that Microsoft has confirmed a serious issue in non-English modern sites after applying the September Cumulative Update of SharePoint 2019.  Several site components will have their text replaced with blanks.

The release notes for the September Cumulative Update have been updated to show this as a "known issue".

We recommend not installing this cumulative update, but waiting for one in which the issue is corrected.  More details can be found in this blog post from Microsoft Senior Escalation Enginee Stefan Gossner.

Update: You can download a fix for this problem https://support.microsoft.com/en-us/help/4461512/september-21-2020-update-for-sharepoint-server-2019-kb4461512

This is a mandatory update release for PointFire 365 for SharePoint Online, part of Office 365. 

This release adds minor new functionality and corrects a number of issues in version 2.4.0.  It also corrects some significant issues that are currently only found in the Targeted Release version of SharePoint Online, and that may appear in the General Availability version at an unknown date.  If you were provided with an interim release since August 13, 2020, you should update to this release.

New and Changed Features

• Microsoft Lists support: Show "Make List Multilingual" option in ribbon and "Manage Variations" option in ECB menu
• Improve design of Manage Variations to make the save/cancel icons and spacing similar to edit form

Resolved Issues

• For some classic pages, page content is blank until a button in the ribbon is clicked
• Language menu was not appearing for some users in targeted release program
• Webparts were showing in all languages despite setting the language of the webparts, users in targeted release program and some others
• On a filtered modern list/library, changing language or navigating to a list on another site resulted in three page reloads. Now down to 1 or 2.
• For some users, the browser would occasionally download a JavaScript file rather than executing it while loading a SharePoint page
• When a page is copied, changing the language of a webpart on one page would change it on the other one.
• Me Control (personal menu) did not always close if the language menu had been expanded/collapsed depending on the location of the click
• Navigation loaded in the wrong language after selecting Unfiltered
• Other instances where the navigation or list filtering was in the wrong language
• Clear the Cache button in PF365 app page was not working properly for Microsoft Edge browser
• List/library setting page had superfluous parameters
• Event list sometimes did not filter by language on Internet Explorer
• Manage Variations not working for event list views
• In edit mode on a new page, webpart filtering sometimes hid a webpart when it should be visible.
• Some instances where the language menu selection spins but does not reload the page.

PointFire makes SharePoint truly multilingual and lets your users collaborate in their language.  Two different users going to the same page on the same site will each see it almost entirely in their language, both UI and content, without using Variations.

To get your copy, go to http://community.icefire.ca/index.php?/Knowledgebase/List/Index/1/pointfire-installation-packages and log in or create an account.

The fully-featured trial version can be downloaded for free and can be used for development and testing, with some pre-sale support.

PointFire Translator version 2.0.0.0 is now available.  Thank you to everyone who participated in the beta versions for the past year.

This is a major upgrade, which includes and requires a new version of the PointFire Translator app, also named version 2.0.0.0.

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.

If you were using version 1.2, the major change is that you do not need to install it on the workstation of the person carrying out the translation (although that is still supported), but it can be on a shared physical or virtual server.  It runs under the identity of the person who called it via the app, it can also be called by Power Automate, and it supports the SharePoint Multilingual Page Publishing feature.

If you were using Beta 2, the major new feature is a PowerShell script to register the app and to create a Custom Connector for Power Automate

New Features

• 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.
• AppReg.ps1 script to automate Azure Application Registration
• Creation of Custom Connector for Power Automate
• 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
• Exclude some strings from translating, or specify the translation
• Better handling of multiple exceptions in Parallel execution
• Added functionality to translate Multilingual Translations list.
• Single sign-on by obtaining access token, including configuration of Translator App
• Support https
• Can be hosted anywhere, not on localhost
• locally stored credentials optional
• locally stored credentials encrypted
• Multiple licensees, API key applies to group of licensees
• License key determines how many users can be licensed, whether domain wildcard is allowed
• Improved security
• Improved logging
• Adjust Office registry setting to prevent popup dialogs
• Improvements in MFA support
• Improved support for 2019 and vanity domains
• Retry after partial translation
• Handle API throttling, other errors
• Alternate API regional endpoints. Not extensively tested. Contact us for details.

Bug fixes and enhancements

• Too many to list 

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

Many thanks to the many testers who helped us get the product to this state.

For more information, contact sales@icefire.ca

This release corrects certain issues.  If you received an interim release from IceFire support for testing, it must be updated with this release.  This release is a bug fix release, with minor functionality changes.  It is recommended that you update if you have encountered the issues that are discussed.

Documentation is available here.  

The next update release is expected in December 2020.

Release Notes – June 16, 2020

Deploying PointFire 2016

It is recommended that you run the installation on the server where Central Administration is located. Once PointFire 2016 is installed on the target server you can deploy the feature by running the PFConfiguration tool:

Start ->PointFire 2016 ->PFConfig

Note: If you experience issues running the configuration tool from the shortcut, you can navigate to the PointFire directory and run PFConfig or one of the installation scripts directly.

C:\Program Files\IceFire\PointFire2016

⦁ PFConfig.exe – PointFire Deployment Manager
⦁ InstallPointFire.ps1 - to install PointFire using PowerShell.
⦁ UpgradePointFire.ps1 - Upgrade PointFire using PowerShell.
⦁ RemovePointFire.ps1 - To retract the solution using PowerShell

Note: Deploying using the scripts requires additional configuration steps. Please see the install guide for detailed information.

Updating PointFire 2016 

If you are updating an existing PointFire 2016 deployment, launch the PointFire Deployment Manager and follow through the upgrade process, or retract then re-deploy PointFire, or navigate to the installation directory to run the upgrade script.
Note: If configuration keys in the web.config files have been edited manually after PFConfig initially set them, using PFConfig to update the PointFire may erase or overwrite some of those keys. For safety, note the values of the keys currently in web.config prior to updating.

Upgrading from PointFire 2013

If you are upgrading from a PointFire 2013 deployment, please consult the PointFire 2013 v1.0 to 2016 v1.0 Upgrade Guide.

New Features

• none

Resolved Issues

• Javascript exception on some versions of IE: Unexpected head-level element encountered outside of "<head>"
• Title in a document set, including breadcrumb and newly created item's title does not translate.
• Wrong view is selected (highlighted) when a view name is translated by PointFire
• Promoted sites title appearing within My Sites - Promoted Sites panel are not translated
• Event log errors appear frequently: "An error occured caching the Top Level Translations (CacheTopLevel)"; "PointFire 2016 (OnPreRender): Thread was being aborted."; "An Error occured Generating the variation File Map (RequestDAta)"

Documentation
Documentation for PointFire 2016 is available to be downloaded from the following links:

PointFire 2016 Installation Guide: 
http://community.icefire.ca/index.php?/Knowledgebase/Article/View/134/0/pointfire-2016-documentation

PointFire 2016 Administrators Guide:

http://community.icefire.ca/index.php?/Knowledgebase/Article/View/134/0/pointfire-2016-documentation

PointFire 2016 Users Guide: 

http://community.icefire.ca/index.php?/Knowledgebase/Article/View/134/0/pointfire-2016-documentation

PointFire 2013 v1.0 to 2016 v1.0 Upgrade Guide: 

http://community.icefire.ca/index.php?/Knowledgebase/Article/View/134/0/pointfire-2016-documentation

Support
We recommend that you, or whoever you designate for support, register an account on the support site http://community.icefire.ca/index.php?/Base/UserRegistration/Register . Support can be obtained by clicking on New Ticket on the site after you login or by sending an e-mail to icefire@wssplus.ca