Alchemy CATALYST 2023 Release Notes
Build 150159
Enhancements:
- XML speed performance improvements when loading XML and TMX files.
- More information written to the "C:\Users\Public\Alchemy Software\Catalyst 2023\dotnetdebug\dotnetdebug.txt" log file. This capturing of debugging information can be enabled via Settings | .NET Settings | Log .NET Exceptions and Debugging Information.
- Some referenced assemblies which were previously reported as missing are now found and correctly loaded.
- When inserting .NET files, a count and description is reported for the resources Catalyst can parse. Unparsable or failed to parse resources are listed for further investigation if necessary.
- In the Application Settings, there are new options to Recover and Delete Autosaved Project files (.atk). Same information also shown in an additional dialog on launch of Catalyst when ATK files are found.
- Tag segmentation options added to the Sentence Delimiters suggestion list.
- Modifications added to the Pseudo Translation settings to exclude the addition of full stops and question marks, which would result in the segment counts increasing.
- Catalyst no longer modifies or changes the case of strings prior to sending to the Acrolinx server to allow server-side settings to be set on Acronyms where necessary.
- 3rd party library upgrades
- Update to Microsoft .NET 6.0 Desktop Runtime 6.0.24 which is installed as a pre-requisite.
Bug Fixes:
- XLIFF 1.2 - some strings are not parsed in - found when there were children and grandchildren of the same tag - resolved.
- During an XLIFF Import, the Import task was aborted if not enough of a segment was translated - resolved.
- Using a TMX file during Concordance could show the same hit multiple times - resolved.
- When String Tables are segmented, the Comparison Expert now takes the correct ID of the segment when matching up to determine Added/Removed items.
- ezScript Alignment - better handling of spaces in the output TTK path.
- User Interface
- In the Application Settings, clicking the Restore Defaults did not disable the Log .NET Exceptions and Debugging Information - resolved.
- With APK files when changing the target language, the language validation is now delayed until the user has finished typing, avoiding a language mismatch message.
Build 150148
Enhancements:
- More exception info written to the .NET debug log file. This information can be gathered by setting the option Log .NET Exceptions and Debugging information found at Settings | File Format Settings | .NET Settings. There is a new View Log button there to open the file from the Public folder directly.
- Catalyst will detect if a save is taking place locally or on a network share; if a save is happening to a network share the file is first saved locally and copied to the location afterwards speeding up the save process.
- Acrolinx Validation Check extended to support Transport Layer Security, TLS, 1.2 and 1.3.
- 3rd party library upgrades
- Reference Browser window updated to use Microsoft Edge WebView2 over the legacy Internet Explorer Browser.
- Update to use Analysis Package GLAP_2023_05-PD8.9.0 which are the libraries used to convert the Documentation file formats.
- Update to Microsoft .NET 6.0 Desktop Runtime 6.0.22 which is installed as a pre-requisite.
Bug Fixes:
- ezParse - add an extension similar to any existing but ending with digit results in rules incorrectly matched - resolved.
- A DLL file extracted under .NET 6 and .NET 7 produced differences in the .resources when comparing at a binary level - resolved.
- ezScript - Silent crash seen via the Event Viewer when working with .Net files and .Net 7.0 runtime - resolved.
Crash Report Investigations:
- Saving a Translation Memory on a network drive was very slow or crashed Catalyst - resolved.
Build 150139
Enhancements:
- XML Edit Methods Dialog
- XPath suggestion prompts appear within the Condition and Store in Translation fields. An XPath Editor can also be invoked for more advanced or longer rules. A right click Context menu will help users when writing their XPath conditions.
- The Segmentation Settings can be launched from the XML Edit Methods Dialog, allowing users to refine the segmentation when writing the rule.
- Edit Methods dialog for ezParse also highlights segmentation in the Preview pane.
- XML Edit Methods remembers the last used files for both the Template and the Preview drop downs.
- User's last size and position of the Edit Methods dialog stored and loaded on next relaunch.
- XML Optimising - Inserting and Leveraging XML files is faster.
- When inserting XML files and presented with Select Rule dialog, users can preview the file with existing rules or create a new rule.
- Adding new extensions to the XML ezParse rule allows the extension to be immediately available when browsing for files.
- Expert reports can be saved directly as HTML files allowing them to be viewed directly in most HTML browsers.
- ezScript - If output path for ezLogFile or Reports doesn't exist, Catalyst now creates them.
- ezScript chm - change for /R Create report command, HTML now default for report output
- Users can now type more text to get to the desired languages in the Source and Target language drop down lists.
- Export Segmentation Settings for some embedded files types, txlf and general XLIFF files now enabled so that Keywords Settings, Parsing Rules and Segmentation Rules are exportable.
- Updated the default parsing rules to include MadCap Flare fllng Skin files. Some old legacy extensions removed from the ezParseRules.ezp file.
- 3rd party library upgrades
- Installers updated to use InstallShield 2023.
- Android APKTool updated to the latest version 2.8.1.
- Update to the latest version of the Codejock ToolkitPro library v22.1.0.
- Update to use Analysis Package GLAP_2023_05-PD8.7.0 which are the libraries used to convert the Documentation file formats.
- Update to Microsoft .NET 6.0 Desktop Runtime 6.0.20 which is installed as a pre-requisite.
Bug Fixes:
- File Support
- Failure to insert .NET 6.0 Resx file when .NET 7.0 was installed - resolved.
- .NET - dll file with icons and images not extracting with an ALINK error: AL1022: Error reading embedded resource - resolved.
- Translated segments in a Resx file not being extracted with source content where the start tags were not on a new line - resolved.
- Json files, if the translation was left empty with no translation the original text was being extracted - resolved.
- Error extracting some APK files - resolved with our upgrade to the latest version of APKTool and using the later aapt2.exe tool in that library.
- XML Parsing - Catalyst treated .xsd files as XML rather than as XML Schema - resolved.
- Cannot uncheck "Extract as Original" option for MadCap and Android APK files in the Navigator tree - resolved.
- For XLIFF files the menu option "Extract as Original" in the Navigator tree was not respected - resolved.
- Multilingual TMX - issues with segmented text when using Join next segment; content was lost in the target - resolved.
- Comparison Expert - now uses IDs in comparison of both segmented and unsegmented Json files.
- Comparison Expert - sorting of results now in segment order.
- An XML line feed was being removed from Translator Toolbar on toggle "Show space markers" - resolved.
- When adding an ezParse file extension, if its text was a subset of an existing filetype it resulted in warning dialog - resolved.
- Catalyst Translator Lite Edition: architecture identifier in the application title added, i.e. 32-bit or 64-bit type - resolved.
- The Context String section was disabled in Edit Methods dialog for text based files - resolved.
Crash Report Investigations:
- Memory Leak detected when Recycle Translations enabled and performing translations - resolved.
Build 150112
New Features:
- Segmentation has been extended to BAML Resources.
Enhancements:
- With GlobalLink Term Manager 7.13, Blacklisted terms became Blocklisted terms - Catalyst enhanced to support this.
- XML Files - Some speed optimisation to determine if a node is visible or not before applying segmentation.
- XPATH Syntax now less restrictive with regards to spaces in the syntax and case used for logical operators.
Bug Fixes:
- ezScript - PowerShell command creating a Catalyst report was not completing - resolved.
- Validate Expert extended to report Clipped text and Overlapping controls on .NET 5, 6 and 7 dialogs.
- File Support
-
- JSON files - some backslashes were removed on extraction - resolved.
- XML files - toggle space marker, removed paragraph marker in the Translator Toolbar - resolved.
- Xliff files - some tags missing on extraction - issue with self-closing <bpt> and <ept> tags - resolved.
- BAML files - improvements in the right click menu option Revert Text to revert only text and not the previously selected settings in the revert dialog.
- IDML/TXLF files - value of some attributes in extracted file was stripped - resolved.
Build 150100
New Features:
- Support added for Markdown file formats.
- Support added for .NET 5.0, 6.0 and 7.0 version file formats.
- Support added for XLIFF 2.0 file formats. You can insert and export to this format. Keywords in this exported format will appear within a <mrk> tag with a "translate=no" attribute.
- Max length added to XML parsers. Localizing XML files with CATALYST 2023, you can effortlessly parse Memos, Inline tags, Context links and now Max sizes.
- Segmentation has been extended to the following types of resources: Win32 String tables, .NET String tables and DDF files.
- Export Segmentation Settings added for Documentation File formats.
- Additional HunSpell dictionaries added.
- Project Workspace - Several options have been added to the Project tabs: Right click to access the contextual menu allowing the user to do multiple tasks.
- The Reference area of the Translator Toolbar can be collapsed when no TM is attached.
- In the Navigator pane, users can filter files by status.
- Quick Search operations can be performed on file names within the Navigator Pane.
Enhancements:
- Tags can be entered as segment delimiters - refer to the help for more info.
- During ezScript Alignment you can set the Title at the same time.
- Passwords in Connector strings in the Translation Memories, Machine Translation and Glossaries are masked.
- Updated and added new Windows 11 Framework language codes in line with the Microsoft supported language list.
- Catalyst installation path added to the registry for lookup. The key is: [HKEY_CURRENT_USER\Software\Alchemy\Alchemy Catalyst 2023\General], with a string value of:
"InstallDir"="C:\\Program Files\\Alchemy Software\\Catalyst 2023\\"
- A hyperlink is visible when a New Build is available. It links directly to download the build.
- Within the Segmentation dialog, users can Import and Export settings directly.
- Improved TBX processing and performance.
- Support for reading TBX 3.0 DCA glossaries.
Bug Fixes:
- Glossary - Catalyst times out because of keyword but only for one string in heavily tagged segment - resolved.
- ezScript Leverage - /D switch now loads the default leverage settings before the leverage task starts.