What's new in translationCore 3.6.4
Mar 21, 2024
- User would be able to see proper display of TranslationAcademy Articles for Right-to-Left languages . #7562
New in translationCore 3.6.2 (Nov 9, 2023)
- Bug Fix:
- User would be able to align text with verse span in wordAlignment tool. #7546
- Shift-click does not selects words already aligned when words fall between the selection. #7555
New in translationCore 3.6.1 (Nov 8, 2023)
- Bug Fix:
- User would be able to align text with verse span in wordAlignment tool.
New in translationCore 3.6.0 (Nov 2, 2023)
- Feature:
- Support for Headers/Front Matter editing and aligning is available. #7536
- Users can now select multiple words in the work bank using shift+Click for aligning in wordAlignment tool. #5885
- Users can now clear ALL alignments using Clear button. #7543
New in translationCore 3.6.0 Lite (Nov 2, 2023)
- Feature:
- Support for Headers/Front Matter editing and aligning is available. #7536
- Users can now select multiple words in the work bank using shift+Click for aligning in wordAlignment tool. #5885
- Users can now clear ALL alignments using Clear button. #7543
New in translationCore 3.5.1 (Sep 11, 2023)
- Bugs:
- Print/Preview now prints Chapter numbers left aligned for Left-to-Right Language #7523
New in translationCore 3.5.0 Pre-release (Aug 1, 2023)
- Features:
- Added Print Preview and Pdf generation for projects #7456
- Updated to use Electronite v22.0.3 and add support for Mac Universal Builds #7443. See the section Mac Only for more details of which install to choose.
- Added support for SIL Charis font #7506. This is a great multilingual font that you may prefer for viewing your language in the translationCore tools or for printing.
- Add support for navigating by reference to Translation Notes/Words #7502
- Added support for future Greek Original Language resources #7458
- Add ability to use QA server in testing new resources before official release #7449
- Bugs:
- Fix for export with alignments or upload with alignments fail in translation Core with empty verses #7511
- Fix for git creating new projects with default branch of main instead of master #7487
- Fix to update original language used in alignments when project is opened #7474
- When User changes GLs in tools, make sure the Original Language for appropriate org is shown in Scripture Pane #7470
New in translationCore 3.4.0 (Oct 11, 2022)
- Features:
- Available smaller translationCore install to minimize disk space used on PCs (see the "How to Install" section for details on where to get the smaller install)
- Added support for verse ranges that span chapter boundaries
- Protect users from doing word alignment with older version of original language than version previously used
- tC now handles " & " for discontiguous original language highlights
- BugsL
- translationWords articles were blank when opening in translationNotes
- translationNotes was crashing on leading zeroes in verse links
- After upgrade, sometimes users could not add new scripture panes in translationNotes and translationWords
- Fix highlighting when there are multiple verses in a check
New in translationCore 3.4.0 Pre-release (Sep 26, 2022)
- update locale.
- update tools with newer locales.
New in translationCore 3.3.0 (Sep 26, 2022)
- Update locale.
- Update tools with newer locales.
New in translationCore 3.3.0 (Aug 29, 2022)
- Features:
- Added the ability to update to pre-release resources and remove them from the application as well. #7343, #7363
- Users can now load Bibles by URL to the Scripture pane. #7375
- Translation Notes and Translation Words checks can be in the latest parascriptural format including reference ranges like 2:1,4. #7188, #7322
- The French locale and resources were updated. #7364
- Bugs:
- Zero-width-spaces and no-break-spaces were causing problems with some of the checks, so now translationCore ignores them. #7333
- The parseq character wasn't visible in the scripture pane, but it is now. #7286
- And more #7353, #7341.
- Additional Known Issues:
- When doing a clean install and including the Git install on Windows, the user may only see a blank white screen for a few minutes while tC completes its first loading process which may take several minutes. Whether or not the blank screen is displayed, the user should end and then restart tC before using it. Follow this issue at #7115.
- Windows Only:
- The installation may include installing an update to the .Net framework. After the installation completes, a .Net install dialog may remain on the screen. If that happens just click Cancel.
- The installation of Git is part of the installation process. If Git 2.35.1 or greater is not already on the computer, ensure the checkbox for installing Git is checked on the installation dialog. At the end of the installation, if automatically starting tC, you may receive a message indicating that Git needs to be installed. If that message appears, just click the “Close translationCore” button, then restart tC (the app, not the installation). In tC 3.2.0, the restart of tC should be run twice.
- After installation, starting the application can take a long time (7+ minutes on some machines). Please be patient. Subsequent launches of tC will be faster, but may still take a few minutes.
New in translationCore 3.2.0 (May 24, 2022)
- Features:
- Added Door43 CatalogNext Support so users will be able to use their self-published resources #7193
- Users can choose to show raw USFM in the scripture pane#7226
- Minor Features:
- tC can now handle TranslationAcademy articles that have a missing title.md files #7250
- Users can cancel out of downloading when downloads are taking too long #7222
- Updates:
- Updated Electronite to use latest Electron Version 17.3.1 #7203 to fix UI issues with Windows 11 #7230
- the git version in Windows installer was updated#7166
- Fixed bugs:
- TranslationNotes with a -1 Occurrence number (meaning highlight all occurences) were not handled #7291 and #7292
- Fixed empty occurrence notes causing a crash when downloading the latest TNs #7213
- Additional Known Issues:
- When doing a clean install and including the Git install on Windows, the user may only see a blank white screen for a few minutes while tC completes its first loading process which may take several minutes. Whether or not the blank screen is displayed, the user should end and then restart tC before using it. Follow this issue at #7115.
New in translationCore 3.1.0 (Feb 2, 2022)
- Features:
- When a target scripture text includes a verse span, tC:
- recognizes them as valid verses
- allows the user to align the verse to the original language
- allows checking the verse with Translation Notes and Translation Words
- allows the user to edit the verse text
- Bug Fixes:
- After a user downloaded the latest content, it was only available until tC was closed. Now the latest content is no longer removed.
New in translationCore 3.0.2 (Dec 21, 2021)
- Fixes:
- Translation Notes were not handling the apostrophe in Greek correctly and some checks were failing because of it. For example ἀλλ’ in 2Tim 3:9. #7156.
- Translation Notes checks were getting interchanged and displayed incorrectly when resources were updated.#7198
- A space was getting added to exported USFM in a couple of instances #7165, #7164.
- Multiple Translation Notes were not allowed for the same words in the original language text. #7096.
- When beginning a Translation Notes check, tC needs the version of the original language that those notes are aligned to. In some cases, tC was not downloading the needed version of the original language and sometimes the user was not warned that an internet connection was needed. #7120, #7140.
- Under certain circumstances, tC wasn’t downloading the original language file needed for doing Translation Notes check. 7121, 7140
- Other bug fixes. 7133, 7162
New in translationCore 3.0.1 (Oct 19, 2020)
- Fixes:
- On both translationNotes (tN) and translationWords (tW) checks, tC displays a quote to be checked by the user. For that quote, version 3.0.1 now uses, by default, the Gateway Language Literal Text (GLT) for the Gateway Language that is selected for the tN or tW tool being used. If the GLT does not have a translation for the verse being checked, tC will look at the manifest.json file for the tool being used and display the quote from the first resource listed in the "relation" section of the manifest file. That field is editable using a text editor, but be careful not to make any other changes to it. The manifest files are located in the path ~translationCoreresources[language code]translationHelps[tool]; e.g. /Users/[user]/translationCore/resources/en/translationHelps/translationNotes.
- When running the feature to “Check for software updates” on Mac systems, previous versions of tC were incorrectly informing the user that tC was up to date. This issue has now been fixed.
New in translationCore 3.0.0 (Sep 22, 2020)
- Major New Features:
- Renders Graphite “smart fonts” for writing systems that have complex behaviors.
- Font Selection - Users can select between the default font vs complex script fonts such as Padauk, Awami Nastaliq, and Scheherazade. Font selection is available on the Project Information page during project importsand via the 3-dot menu on the Projects page, as well as via the 3-dot menu in various places within each of the tools.
- Text resizing is now available for all scripture resources which allows users to increase or decrease font size based on their preference. Text resizing is available via the 3-dot menu in various places within each of the tools.
- Migration to Electronite based on Electron v7 - Updating to Electron v7.0.0 greatly improved the overall performance and security of the app and enhanced our software stack. Also, build sizes are now more consistent across the different operating systems.
- Archiving projects in tC - projects can be archived locally on the user’s machine so that they are removed from the project list displayed within tC. Projects are best restored by importing them from Door43.
- Other New Features and Bug Fixes:
- Improved handling of right-to-left text alignment within tC.
- A number of performance issues were addressed. There have been noticeable performance improvements in many areas of the app.
- TranslationAcademy links in translationNotes now open up in the expanded translation helps pane.
- Added more informative alerts for network communications issues.
- Removed the book name from the group menu panel in order to display the relevant content.
- A number of critical errors were fixed for the import process.
- The WordAlignment tool now allows users to edit scripture (without opening the expanded scripture pane), and to add comments and bookmarks.
- In the WordAlignment tool the width of the word cards in the word bank now resize automatically.
- The translationCore build now includes resources from all languages that currently have aligned texts.
- Known Bugs and Issues:
- The first time a user runs tC, when upgrading from 1.1.4 or previous, a message will be displayed indicating that their login has become invalid and they need to log out and log back in. This is intentional and is needed in order to take advantage of the new security enhancements to Door43.
- In the Word Alignment tool, filtering the navigation menu for unaligned words will not always show the correct results (track here).
- When a user reimports a project causing an overwrite, the previous selections for a Gateway Language on the tool cards are not persisted and the user must reselect the GL from which to check (track here).
- If a user reimports a project, the invalidations counter on the Word Alignment tool card is not automatically updated and can be out of sync with the actual number of reset alignments in the project (track here).
- Suggestions in the Word Alignment tool sometimes appear out of order for multiple instances of the same word (track here).
- If a user imports a USFM file that contains alignments, all of the “Alignment Complete” toggles in the Word Alignment tool will be turned off and the percentage complete on the Word Alignment tool card will display 0% (track here).
- There are several situations that are causing the percent complete indicated on the Word Alignment tool card to not be correct (track here).