translationCore v3.3.0

translationCore v3.3.0 Release Notes

translationCore is free, and both the software and all its content are open-licensed. We pray that this software will help to check Bible translations and will result in the growth and strengthening of the Church.

Release 3.3.0 Overview

The focus of v3.3.0 is to support access to pre-released content on Door43.

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.
• After upgrading from older version of translationCore, can have problem adding scripture panes in the translationNotes and translationWords tools (not all downloaded bibles are shown). The work around is to switch to wordAlignment tool and add scripture panes in that tool. Then when you switch back to translationNotes or translationWords tools you will also see the added scripture panes. Follow this issue at #7414

How to Install

The installation files are available on the translationCore v3.3.0 release page or go to https://translationcore.com.

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.3.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.

Mac Only

• It might take a few minutes to open tC the first time. Please be patient.

• If you get a message about Git being required, you will need to open your terminal and run:
  xcode-select --install
sudo xcode-select -s /Library/Developer/CommandLineTools

• If this does not work, you can launch the app from the command line. Open the terminal and run:
  /Applications/translationCore.app/Contents/MacOS/translationCore

We Need Your Help!

There are two major ways you can help us improve translationCore:

• Leave user feedback - As you find bugs, nuisances, typos, or have other suggested improvements for tC, please use the user feedback to send us those suggestions! (Go to the Actions menu and click “User Feedback”.)
• App Localization - If you notice that some of the translated user interface can be improved or if you would like tC to be localized to a new language, you can help! We are using a crowd-sourced platform to localize translationCore. Localization text for tC is spread across three projects: https://crowdin.com/project/translationcore, https://crowdin.com/project/translationwords, https://crowdin.com/project/translationnotes, and https://crowdin.com/project/wordalignment. To help, you must create a user profile, select the correct language, find the correct word or phrase that needs to be improved, and suggest a change! If you would like to start a new language, contact us at [email protected] and we’ll complete the initial setup for you. (Note: all changes will be incorporated in the next release of tC.)

Downloads

translationCore v3.2.0

translationCore v3.2.0 Release Notes

translationCore is free, and both the software and all its content are open-licensed. We pray that this software will help to check Bible translations and will result in the growth and strengthening of the Church.

Release 3.2.0 Overview

The focus of v3.2.0 was support for the new catalog features on the Door43 Content Service.

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.

How to Install

The installation files are available on the translationCore v3.2.0 release page or go to https://translationcore.com.

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.

Mac Only

• It might take a few minutes to open tC the first time. Please be patient.

• If you get a message about Git being required, you will need to open your terminal and run:
  xcode-select --install
sudo xcode-select -s /Library/Developer/CommandLineTools

• If this does not work, you can launch the app from the command line. Open the terminal and run:
  /Applications/translationCore.app/Contents/MacOS/translationCore

We Need Your Help!

There are two major ways you can help us improve translationCore:

• Leave user feedback - As you find bugs, nuisances, typos, or have other suggested improvements for tC, please use the user feedback to send us those suggestions! (Go to the Actions menu and click “User Feedback”.)
• App Localization - If you notice that some of the translated user interface can be improved or if you would like tC to be localized to a new language, you can help! We are using a crowd-sourced platform to localize translationCore. Localization text for tC is spread across three projects: https://crowdin.com/project/translationcore, https://crowdin.com/project/translationwords, https://crowdin.com/project/translationnotes, and https://crowdin.com/project/wordalignment. To help, you must create a user profile, select the correct language, find the correct word or phrase that needs to be improved, and suggest a change! If you would like to start a new language, contact us at [email protected] and we’ll complete the initial setup for you. (Note: all changes will be incorporated in the next release of tC.)

Downloads

translationCore v3.1.0

translationCore v3.1.0 Release Notes

translationCore is free, and both the software and all its content are open-licensed. We pray that this software will help to check Bible translations and will result in the growth and strengthening of the Church.

Release 3.1.0 Overview

The focus v3.1.0 is to add in support for verse spans (two verses combined as one typically due to a grammar requirement).

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.

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.

How to Install

The installation files are available on the translationCore v3.1.0 release page or go to https://translationcore.com.

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.9.2 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.1.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.

Mac Only

• Install the latest Git if Git 2.9.2 if it is not already on the computer.

  • Go to https://git-scm.com/download/mac 2 and the executable should automatically download.
  • If your download hasn’t started, click the link that says “Click here to download manually.”
  • Open the downloaded file
  • If your Mac’s permissions did not allow the installation to start then follow the following instructions:
  • Go to System preferences
  • Open Security & privacy
  • Click on the “Open anyway” button at the bottom
  • Then click open
  • The installation should automatically start.
  • Click continue
  • Then Install

• It might take a few minutes to open tC the first time. Please be patient.

• If you get a message about Git being required, you will need to open your terminal and run:
  xcode-select --install
sudo xcode-select -s /Library/Developer/CommandLineTools

• If this does not work, you can launch the app from the command line. Open the terminal and run:
  /Applications/translationCore.app/Contents/MacOS/translationCore

We Need Your Help!

There are two major ways you can help us improve translationCore:

• Leave user feedback - As you find bugs, nuisances, typos, or have other suggested improvements for tC, please use the user feedback to send us those suggestions! (Go to the Actions menu and click “User Feedback”.)
• App Localization - If you notice that some of the translated user interface can be improved or if you would like tC to be localized to a new language, you can help! We are using a crowd-sourced platform to localize translationCore. Localization text for tC is spread across three projects: https://crowdin.com/project/translationcore, https://crowdin.com/project/translationwords, https://crowdin.com/project/translationnotes, and https://crowdin.com/project/wordalignment. To help, you must create a user profile, select the correct language, find the correct word or phrase that needs to be improved, and suggest a change! If you would like to start a new language, contact us at [email protected] and we’ll complete the initial setup for you. (Note: all changes will be incorporated in the next release of tC.)

Downloads

translationCore v3.0.2

translationCore v3.0.2 Release Notes

translationCore is free, and both the software and all its content are open-licensed. We pray that this software will help to check Bible translations and will result in the growth and strengthening of the Church.

Release 3.0.2 Overview

v3.0.2 is a hotfix to address a number of issues with how tC handles the content of the checks and the exporting and importing of projects.

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

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.

How to Install

The installation files are available on the translationCore v3.0.2 release page or go to https://translationcore.com.

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.9.2 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.0.2, 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.

Mac Only

• Install the latest Git if Git 2.9.2 if it is not already on the computer.
  • Go to https://git-scm.com/download/mac 2 and the executable should automatically download.
  • If your download hasn’t started, click the link that says “Click here to download manually.”
  • Open the downloaded file
  • If your Mac’s permissions did not allow the installation to start then follow the following instructions:
  • Go to System preferences
  • Open Security & privacy
  • Click on the “Open anyway” button at the bottom
  • Then click open
  • The installation should automatically start.
  • Click continue
  • Then Install
• It might take a few minutes to open tC the first time. Please be patient.
• If you get a message about Git being required, you will need to open your terminal and run:
  xcode-select --install
  sudo xcode-select -s /Library/Developer/CommandLineTools
• If this does not work, you can launch the app from the command line. Open the terminal and run:
  /Applications/translationCore.app/Contents/MacOS/translationCore

We Need Your Help!

There are two major ways you can help us improve translationCore:

• Leave user feedback - As you find bugs, nuisances, typos, or have other suggested improvements for tC, please use the user feedback to send us those suggestions! (Go to the Actions menu and click “User Feedback”.)
• App Localization - If you notice that some of the translated user interface can be improved or if you would like tC to be localized to a new language, you can help! We are using a crowd-sourced platform to localize translationCore. Localization text for tC is spread across three projects: https://crowdin.com/project/translationcore, https://crowdin.com/project/translationwords, https://crowdin.com/project/translationnotes, and https://crowdin.com/project/wordalignment. To help, you must create a user profile, select the correct language, find the correct word or phrase that needs to be improved, and suggest a change! If you would like to start a new language, contact us at [email protected] and we’ll complete the initial setup for you. (Note: all changes will be incorporated in the next release of tC.)

Downloads

translationCore v3.0.1

translationCore v3.0.1 Release Notes

translationCore is free, and both the software and all its content are open-licensed. We pray that this software will help to check Bible translations and will result in the growth and strengthening of the Church.

Release 3.0.1 Overview

v3.0.1 is a hotfix to help with using newly published Gateway Language content for checking, and for updating the software to the latest release. If you have experienced either of these issues, please install this new version using the links below.

Fixes

• The logic for choosing which Gateway Language Bible version is used to display the quoted text in the "select the translation for" prompt. The new logic is as follows:

  • tC will first check the 'related' field of the TN or TW manifest file and choose the first Gateway Language Bible version that has an alignment for that check.
  • If tC doesn't find a match it will search for a GLT version for that language
  • if no match is found in any of the above tC will search for any other Bibles in that language.

• 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.

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.

How to Install

The installation files are available on the translationCore v3.0.1 release page or go to https://translationcore.com.

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.9.2 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.0.1, 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.

Mac Only

• Install the latest Git if Git 2.9.2 if it is not already on the computer.

  • Go to https://git-scm.com/download/mac 2 and the executable should automatically download.
  • If your download hasn’t started, click the link that says “Click here to download manually.”
  • Open the downloaded file
  • If your Mac’s permissions did not allow the installation to start then follow the following instructions:
  • Go to System preferences
  • Open Security & privacy
  • Click on the “Open anyway” button at the bottom
  • Then click open
  • The installation should automatically start.
  • Click continue
  • Then Install

• It might take a few minutes to open tC the first time. Please be patient.

• If you get a message about Git being required, you will need to open your terminal and run:
  xcode-select --install
sudo xcode-select -s /Library/Developer/CommandLineTools

• If this does not work, you can launch the app from the command line. Open the terminal and run:
  /Applications/translationCore.app/Contents/MacOS/translationCore

We Need Your Help!

There are two major ways you can help us improve translationCore:

• Leave user feedback - As you find bugs, nuisances, typos, or have other suggested improvements for tC, please use the user feedback to send us those suggestions! (Go to the Actions menu and click “User Feedback”.)
• App Localization - If you notice that some of the translated user interface can be improved or if you would like tC to be localized to a new language, you can help! We are using a crowd-sourced platform to localize translationCore. Localization text for tC is spread across three projects: https://crowdin.com/project/translationcore, https://crowdin.com/project/translationwords, https://crowdin.com/project/translationnotes, and https://crowdin.com/project/wordalignment. To help, you must create a user profile, select the correct language, find the correct word or phrase that needs to be improved, and suggest a change! If you would like to start a new language, contact us at [email protected] and we’ll complete the initial setup for you. (Note: all changes will be incorporated in the next release of tC.)

Downloads

translationCore v3.0.0

translationCore v3.0.0 Release Notes

translationCore is free, and both the software and all its content are open-licensed. We pray that this software will help to check Bible translations and will result in the growth and strengthening of the Church.

Release 3.0 Overview

The focus of 3.0.0 is to enable complex script to support Bible translation in languages such as Arabic and Burmese. Enabling complex scripts in tC involved a major migration to a new platform known as ‘Electronite’. Electronite is a customized version of the Electron framework developed for tC 3.0 that utilizes SIL’s font rendering system Graphite.

Learn More about Electronite:

Electronite Wiki
Video Walkthroughs

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).

How to Install

The installation files are available on the translationCore v3.0 release page or go to https://translationcore.com.

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.9.2 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).
• 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.

Mac Only

• Install the latest Git if Git 2.9.2 if it is not already on the computer.
  • Go to https://git-scm.com/download/mac 2 and the executable should automatically download.
  • If your download hasn’t started, click the link that says “Click here to download manually.”
  • Open the downloaded file
  • If your Mac’s permissions did not allow the installation to start then follow the following instructions:
  • Go to System preferences
  • Open Security & privacy
  • Click on the “Open anyway” button at the bottom
  • Then click open
  • The installation should automatically start.
  • Click continue
  • Then Install
• It might take a few minutes to open tC the first time. Please be patient.
• If you have updated to High Sierra and get a message about Git being required, you will need to open your terminal and run:

xcode-select --install

• If you have updated to Mojave or Catalina and get a message about Git being required, you will need to open your terminal and run:

xcode-select --install

sudo xcode-select -s /Library/Developer/CommandLineTools

• If this does not work, you can launch the app from the command line. Open the terminal and run:

/Applications/translationCore.app/Contents/MacOS/translationCore

We Need Your Help!

There are two major ways you can help us improve translationCore:

• Leave user feedback - As you find bugs, nuisances, typos, or have other suggested improvements for tC, please use the user feedback to send us those suggestions! (Go to the Actions menu and click “User Feedback”.)
• App Localization - If you notice that some of the translated user interface can be improved or if you would like tC to be localized to a new language, you can help! We are using a crowd-sourced platform to localize translationCore. Localization text for tC is spread across three projects: https://crowdin.com/project/translationcore, https://crowdin.com/project/translationwords, https://crowdin.com/project/translationnotes, and https://crowdin.com/project/wordalignment. To help, you must create a user profile, select the correct language, find the correct word or phrase that needs to be improved, and suggest a change! If you would like to start a new language, contact us at [email protected] and we’ll complete the initial setup for you. (Note: all changes will be incorporated in the next release of tC.)

Downloads

translationCore v2.1.2

translationCore v2.1.2 Release Notes

translationCore is free, and both the software and all its content are open-licensed. We pray that this software will help to check Bible translations and will result in the growth and strengthening of the Church.

Release 2.1.2 Overview

v2.1.2 is a hotfix to address specific issues because hotfixes do that sort of thing :) If you have experienced this issue, please install this new version using the links below.

Fixes

• tC was reporting a "problem with the content" in a number of the translationNotes checks in the book of Ruth. It turns out tC was not correctly parsing a couple of Hebrew characters. It will now properly handle the zero-width joiner (U+2060) and the Maqaf (U+05BE).

How to Install

The installation files are available on the translationCore v2.1.2 release page or go to https://translationcore.com.

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.9.2 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).
• 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.

Mac Only

• Install the latest Git if Git 2.9.2 if it is not already on the computer.
  • Go to https://git-scm.com/download/mac 2 and the executable should automatically download.
  • If your download hasn’t started, click the link that says “Click here to download manually.”
  • Open the downloaded file
  • If your Mac’s permissions did not allow the installation to start then follow the following instructions:
  • Go to System preferences
  • Open Security & privacy
  • Click on the “Open anyway” button at the bottom
  • Then click open
  • The installation should automatically start.
  • Click continue
  • Then Install
• It might take a few minutes to open tC the first time. Please be patient.
• If you have updated to High Sierra and get a message about Git being required, you will need to open your terminal and run:

xcode-select --install

• If you have updated to Mojave or Catalina and get a message about Git being required, you will need to open your terminal and run:

xcode-select --install

sudo xcode-select -s /Library/Developer/CommandLineTools

• If this does not work, you can launch the app from the command line. Open the terminal and run:

/Applications/translationCore.app/Contents/MacOS/translationCore

We Need Your Help!

There are two major ways you can help us improve translationCore:

• Leave user feedback - As you find bugs, nuisances, typos, or have other suggested improvements for tC, please use the user feedback to send us those suggestions! (Go to the Actions menu and click “User Feedback”.)
• App Localization - If you notice that some of the translated user interface can be improved or if you would like tC to be localized to a new language, you can help! We are using a crowd-sourced platform to localize translationCore. Localization text for tC is spread across three projects: https://crowdin.com/project/translationcore, https://crowdin.com/project/translationwords, https://crowdin.com/project/translationnotes, and https://crowdin.com/project/wordalignment. To help, you must create a user profile, select the correct language, find the correct word or phrase that needs to be improved, and suggest a change! If you would like to start a new language, contact us at [email protected] and we’ll complete the initial setup for you. (Note: all changes will be incorporated in the next release of tC.)

Downloads

translationCore v2.1.1

translationCore v2.1.1 Release Notes

translationCore is free, and both the software and all its content are open-licensed. We pray that this software will help to check Bible translations and will result in the growth and strengthening of the Church.

Release 2.1.1 Overview

v2.1.1 is a hotfix to address specific issues, because hotfixes do that sort of thing :) If you have experienced any of these issues, please install this new version using the links below.

Fixes

• When exporting a project, the screen was dimmed and the alert was disabled. If the export failed, the user could not click the disabled alert and continue. This was unfortunate, but now, even if the export fails, the user can continue working.
• A number of checks in the translationNotes tool contain the ellipsis character (…) and translationCore marked those checks as having a problem with the content of the check. tC was wrong and we’re sorry.
• translationCore now warns users that some previous checks might be invalidated if the Gateway Language for translationNotes doesn’t use the same Greek or Hebrew text as translationWords or wordAlignment.

How to Install

The installation files are available on the translationCore v2.1.1 release page or go to https://translationcore.com.

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.9.2 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).
• 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.

Mac Only

• Install the latest Git if Git 2.9.2 if it is not already on the computer.
  • Go to https://git-scm.com/download/mac 2 and the executable should automatically download.
  • If your download hasn’t started, click the link that says “Click here to download manually.”
  • Open the downloaded file
  • If your Mac’s permissions did not allow the installation to start then follow the following instructions:
  • Go to System preferences
  • Open Security & privacy
  • Click on the “Open anyway” button at the bottom
  • Then click open
  • The installation should automatically start.
  • Click continue
  • Then Install
• It might take a few minutes to open tC the first time. Please be patient.
• If you have updated to High Sierra and get a message about Git being required, you will need to open your terminal and run:

xcode-select --install

• If you have updated to Mojave or Catalina and get a message about Git being required, you will need to open your terminal and run:

xcode-select --install

sudo xcode-select -s /Library/Developer/CommandLineTools

• If this does not work, you can launch the app from the command line. Open the terminal and run:

/Applications/translationCore.app/Contents/MacOS/translationCore

We Need Your Help!

There are two major ways you can help us improve translationCore:

• Leave user feedback - As you find bugs, nuisances, typos, or have other suggested improvements for tC, please use the user feedback to send us those suggestions! (Go to the Actions menu and click “User Feedback”.)
• App Localization - If you notice that some of the translated user interface can be improved or if you would like tC to be localized to a new language, you can help! We are using a crowd-sourced platform to localize translationCore. Localization text for tC is spread across three projects: https://crowdin.com/project/translationcore, https://crowdin.com/project/translationwords, https://crowdin.com/project/translationnotes, and https://crowdin.com/project/wordalignment. To help, you must create a user profile, select the correct language, find the correct word or phrase that needs to be improved, and suggest a change! If you would like to start a new language, contact us at [email protected] and we’ll complete the initial setup for you. (Note: all changes will be incorporated in the next release of tC.)

translationCore v2.1.0

2.1 Release Notes

translationCore is free and both the software and all its content are open-licensed. It is our prayer that this software will help facilitate the checking of Bible translations and will result in the growth and strengthening of the Church.

Warning: This upgrade is not backward compatible to translationCore versions before 2.1.0. Before upgrading, please backup your projects by clicking the 3 dot menu for each project on the projects page and choose 'upload to door43'. Please note: Once a project is uploaded to Door43 from translationCore 2.1, that project cannot be opened by previous versions of translationCore. Other users will need to upgrade to version 2.1 in order to import that project from Door43.

Release 2.1 Overview

This release of translationCore adds some needed processing notifications, better communication with the latest upgrades to Door43, and several bug fixes.

Major New Features

No major new features were included in this release.

Other New Features and Bug Fixes

• Changes to Door43 required updates to the way user logins are handled. In most cases users will receive a “your login has become invalid” alert and will need to log out and log back in to Door43 after upgrading to version 2.1. tC has been updated to handle the new user validation process and some other recent improvements to Door43. These changes also addressed tC reporting that creating a new repository on Door43 had failed even though it was successful.
• Processing notifications - Some long processes were running in the background without any indication that they were taking place. Processing notifications were added to these operations.
• Performance improvements - Some processes in tW are now as much as 50% faster. There are more performance improvements to come in 2020!
• Fixed wrong selection info - Under certain circumstances, the wrong selection information was displayed in the navigation menu in the tN tool.
• Localization fixes - Changing locales did not immediately affect the user interface on all screens. Now it does!
• Percentage complete - The percentages indicated on the tool cards were not always accurate. This bug caused the card to sometimes indicate 100% even though there were a few missing checks or alignments. Now the percentages complete will not show 100% until every check or alignment has been completed, and it will show “<1%” if only a few have been completed, but not yet 1% of them.

Known Bugs and Issues

• The first time a user runs tC after upgrading to version 2.1 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.
• Some content will show formatting characters in the translationNotes tool (track here).
• 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 alignemnts, 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).

How to Install

The installation files are available on the translationCore v2.1 release page or go to https://translationcore.com.

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.9.2 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).
• 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.

Mac Only

• Install latest Git if Git 2.9.2 if it is not already on the computer.
  • Go to https://git-scm.com/download/mac 2 and the executable should automatically download.
  • If your download hasn’t started, click the link that says “Click here to download manually.”
  • Open the downloaded file
  • If your Mac’s permissions did not allow the installation to start then follow the following instructions:
  • Go to System preferences
  • Open Security & privacy
  • Click on the “Open anyway” button at the bottom
  • Then click open
  • The installation should automatically start.
  • Click continue
  • Then Install
• It might take a few minutes to open tC the first time. Please be patient.
• If you have updated to High Sierra and get a message about Git being required, you will need to open your terminal and run:

xcode-select --install

• If you have updated to Mojave or Catalina and get a message about Git being required, you will need to open your terminal and run:

xcode-select --install

sudo xcode-select -s /Library/Developer/CommandLineTools

• If this does not work, you can launch the app from the command line. Open the terminal and run:

/Applications/translationCore.app/Contents/MacOS/translationCore

We Need Your Help!

There are two major ways you can help us improve translationCore:

• Leave user feedback - As you find bugs, nuisances, typos, or have other suggested improvements for tC, please use the user feedback to send us those suggestions! (Go to the Actions menu and click “User Feedback”.)
• App Localization - If you notice that some of the translated user interface can be improved or if you would like tC to be localized to a new language, you can help! We are using a crowd-sourced platform to localize translationCore. Localization text for tC is spread across three projects: https://crowdin.com/project/translationcore, https://crowdin.com/project/translationwords, https://crowdin.com/project/translationnotes, and https://crowdin.com/project/wordalignment. To help, you must create a user profile, select the correct language, find the correct word or phrase that needs to be improved, and suggest a change! If you would like to start a new language, contact us at [email protected] and we’ll complete the initial setup for you. (Note: all changes will be incorporated in the next release of tC.)

translationCore v2.0.0

2.0 Release Notes

Release 2.0 Overview

This release of translationCore marks a momentous occasion for Bible translation! For the first time in history, a translator can check their translation by working through a pre-identified list of checks that identify Figures of Speech. Each translationNotes check has a unique description for that instance as well as a generic article describing the category (e.g. “Metaphor,” “Synecdoche,” “Metonymy,” etc.) and identifying good translation practice. As with the translationWords tool, these checks are presented in a pivoted view so that all checks within a category are presented together before progressing to the next category. Finally, all of these checks are designed to be translated into Gateway Languages and presented in translationCore in a language the translator understands well.

Additionally, enhancements have been made to the translationWords tool and it has been enhanced to support the whole Bible. Finally, the Word Alignment tool has seen multiple enhancements including Alignment Memory being drawn from across an entire Testament (rather than just one book).

Major New Features

• translationNotes tool - This tool functions exactly like the translationWords tool but presents the user with different checks based on different content. Each check highlights a word or phrase to be checked and presents a unique note for that instance (in the blue Check Info Bar). The user is also presented with a translationAcademy article describing the type of check it is, for instance, “Metaphor,” “Synecdoche,” “Metonymy,” etc. (in the gray translationHelps Pane). When loading the tool, the user can select which types of checks they want to perform. For convenience, all these have been organized into these categories: “Culture,” “Discourse,” “Figures of Speech,” “Grammar,” “Numbers,” and “Other”.
• Allow checking for any “unlocked” Old Testament Book - Now any book of the Bible can be checked from any Gateway Language with both translationWords and translationNotes, dependent upon content requirements being met. To check a book of the Bible in either tool, the Gateway Language must have that book aligned to the UGNT or UHB. Furthermore, to check with the translationWords tool, translationWords must be translated. To check with the translationNotes tool, translationAcademy must be translated and the translationNotes for that book must be translated. (Note: All content must be published to the Door43 Catalog. To check for updated content, click Action / Check for Content Updates. If content updates result in the content requirements being met, those books will automatically be “unlocked” for that Gateway Language in tC.)
• “No Selection Needed” toggle - This feature was added to the translationWords and translationNotes tools. It allows a user to indicate that the check was completed, even if there is no selection that can be made. Toggling “No Selection Needed” will result in the green checkmark showing in the navigation menu. A new filter was also added so that a user can find all checks where “Not Selection Needed” was toggled on.
• Discontiguous merging of Original Language words - In the Word Alignment tool, any Original Language word may now be merged with any other Original Language word. (This feature allows a phrase like “ὁ δὲ θεὸς” to be aligned more granularaly as “δὲ” > “but” and “ὁ + θεὸς” > “God” instead of forcing the whole phrase to be aligned like this: “ὁ δὲ θεὸς” > “but God”.)
• Whole language Alignment Memory - In the Word Alignment tool, every alignment is saved as “Alignment Memory”. Any time the user navigates to a new verse, translationCore scans the Alignment Memory to see if there is a match between the Target Language words in the Word Bank and the Original Language words in the Alignment Pane. All matches are suggested to the user and can be accepted or rejected. All Alignment Memory is constrained by the language and identifier (think “NIV”, “KJV”, etc.). With this feature, Alignment Memory is now drawn from across the entire Testament (instead of just that book). In this way, alignments done in Matthew will now populate alignment suggestions in Mark (and alignments from Matthew and Mark will populate suggestions for Luke, etc.)

Other New Features and Bug Fixes

• Multiple Greek New Testaments available for reference - Though the data in translationCore is still based off of the unfoldingWord Green New Testament (UGNT), the Majority Text and Tischendorf have been added as reference texts. (Note: these are not bundled with tC, but can be downloaded via “Source Content Update”.)
• Bug fix for exporting Revelation Projects - A bug was fixed that prevented Revelation projects from being exported. Another bug was fixed that falsely reported successful export even though it actually failed.
• Downloaded Bibles are retained when tC is updated - A bug was fixed that deleted all non-bundled Bible resources when tC was upgraded. Now these resources do not need to be re-downloaded and are immediately available for viewing upon upgrade.
• Hebrew font updated - The bundled font used to display Hebrew was updated so that it now displays correctly on all computers and operating systems.
• Bug fix for spinning logo processing screens - A bug was fixed that cause the spinning tC logo indicating processing is taking place to sometimes not display right away.
• Performance enhancements for “Checking for invalidations” - Optimization to speed the process of checking for breaking changes.
• Bug fix to clear “activated” words - In the Word Alignment tool, Target Words in the Word Bank can be “activated” for multi-select. Now they are “de-activated” when the user opens a dialog or navigates to a different verse.
• Multiple panes now draggable - The Expanded Scripture Pane, the Edit Pane, and the Expanded Translation Helps Pane are all draggable so that the user can see what is underneath them.
• New filter in Word Alignment Tool - The new “Unaligned words” filter will only display verses that have either a Target Word or an Original Language word that is unaligned.
• Bug fix to prevent text overflow - A bug was fixed that caused very long verses to overflow in the verse check pane in the tW tool.
• Optimizations to “Update Gateway Language Content” downloader - When downloading multiple resources, this feature would sometimes fail, now fixed.
• Unnecessary tool reload removed - Now a user can go back and forth between the stepper and the loaded tool without reloading the tool, unless the project, Gateway Language, tool, or types of checks on the Tool card are changed.
• Gateway Language selections are persisted - When a user selects a Gateway Language from which to check their project, this selection is now persisted for that project.

Known Bugs

• Sometimes wrong selection info displayed in navigation menu in tN tool - If a book has multiple checks in the same verse for a given category, if the user exits the tool and re-enters the tool, one of the checks may display the wrong information (track here).
• Previous GL selection not persisted after project reimport - When a user reimports a project, previous choices for GLs on the tool cards are not persisted and the user must reselect the GL from which to check (track here).
• After reimport, invalidations counter on tool card not updated - If a user reimports a project, the invalidations counter is not updated and can be out of sync with the actual number of invalidations a project has (track here).
• Changing locale while on Tools page does not propagate right away - If locale is changed while on Tools page, the user must do something before the change actually appears on the screen (track here).
• Percentage complete not always accurate - On the tool cards, the percentage complete indicator will sometimes indicate 100% even if there are missing checks or alignments (track here).
• Suggestions in Word Alignment tool are sometimes out of order - Suggestions in the Word Alignment tool sometimes appear out of order for multiple instances of the same word (track here).
• Alignment Complete toggle not persisted on import - If a user imports a USFM3 file, all the “Alignment Complete” toggles will be turned off and progress will display as 0% (track here).
• When creating new repo, a failure message is displayed even if successful - If a user changes the information about a project and selects to create a new repo, a failure message is thrown even when it is successful, and the failure message states that it was not renamed even though that was not the chosen action (track here).

How to Install

The installation files are available on the translationCore v2.0 release page or go to https://translationcore.com.

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.9.2 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 t...