Forget-me-not Changelog

What's new in Forget-me-not 1.2

Jan 19, 2022
  • If a system change is detected, your license is now reactivated automatically, so there is no need to deactivate the current license and then re-activate it.
  • If you cannot activate or deactivate your license due to Internet connectivity, you can now click “Trouble activating/deactivating” button in About dialogue or the appropriate menu item in Help menu (in the standalone app) for manual license activation and deactivation.
  • If you cannot activate a trial version due to Internet connectivity, you can now click “Trouble activating/deactivating” button in About dialogue or the appropriate menu item in Help menu (in the standalone app) for manual trial activation.
  • Updated the program in accordance with the import capabilities of the latest versions of supported CAT tools: memoQ 9.9, SDL Trados Studio 2021 SR2, Memsource Cloud as of 2022-01-15.
  • In some cases, documents could not be processed because of restricted permissions caused by the document preview in File Open dialogue. This has been fixed.
  • Improved the reliability and accuracy of extracting tracked changes from Word documents.
  • Added configuration buttons in the summary report to allow configuration of the following parameters: 1) whether content items in a specific category should be hidden by default (i.e. the category is not expanded by default), 2) whether all content items in a specific category should be excluded from the detailed report by default. You can use this functionality to ignore certain categories of content, e.g. tracked changes in Word documents or content of master slides in PowerPoint presentations.
  • Improved support for multiple-monitors in the Word and PowerPoint plug-ins: dialogs are now opened on the same monitor as the current window of Microsoft Word or PowerPoint.

New in Forget-me-not 1.1.2 (Sep 21, 2021)

  • Fixed an issue in the 32-bit version of Word 2019.

New in Forget-me-not 1.1.1 (Jul 9, 2021)

  • Tab characters between words were not detected in Word documents. This is now fixed.