translationCore v1.1.4

1.1.4 Release Notes

Release 1.1.4 Overview

This release includes patches for a formatting bug, performance issues, and several other bug fixes.

Major New Features

No major new features were included in this release.

Other New Features and Bug Fixes

• translationWords displayed correctly - A bug was fixed so that translationWords that span multiple Original Words are now displayed correctly in both the Original and Gateway Languages.
• Language lookup by Anglicized name - A bug was fixed so that now languages can be looked up by Anglicized name, in addition to localized name (as available) and language code.
• Bug fix for edit icon display - A bug was fixed so that now the edit icon (pencil) in the side menu remains in-sync with the data.
• Latest resources added to build - The latest tC resource again are bundled with the build.
• “Alignment complete” no longer incorrectly set by tC - tC now persists how the user sets the “Alignment complete” toggle.
• Performance improvements for opening highly edited projects - Significant (~90%) reduction in loading time for projects with many edits.
• tC prevents backwards incompatible projects from importing - A bug was fixed that allowed projects from a newer version of tC that contained a breaking change to be imported into an older version of tC causing it to crash.
• Updated Greek Lexicon - The latest unfoldingWord Greek Lexicon was updated.
• Only one check highlighted at a time - A bug was fixed that allowed two checks to be selected in the side menu at the same time.

Known Bugs

• UST & UHB are not up to date - These resources were updated during the QA soak, so they are not up to the latest. To update to the latest, go to “Source Content Updater” and update the English and Hebrew.
• Projects reimported into 1.1.2 - If a project is imported into 1.1.2, then exported, then reimported into 1.1.2, many *s are added to the text. This bug was fixed in 1.1.3 if data corruption has not already taken place. Note: This means if a project is imported once into 1.1.2, then opened in 1.1.3, no data corruption problems occur. If the same project has been imported twice into 1.1.2, data corruption has occurred. In this case please contact us at [email protected]. To avoid this from happening, please upgrade all users to 1.1.4 immediately!
• Slow performance checking for invalidations - After editing a verse, an automated automated verification is performed to see if this edit has invalidated any previous work. In certain circumstances, this process is unacceptably slow. (Track here)

How to Install

The installation files are available on the translationCore v1.1.4 release page.

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

translationCore v1.1.3

1.1.3 Release Notes

Release 1.1.3 Overview

This release includes patches for a formatting bug, performance issues, and several other bug fixes.

Major New Features

No major new features were included in this release.

Other New Features and Bug Fixes

• Fix formatting bug - This bug improperly handled spacing surrounding punctuation. Fixing this allows the user to import and then export a project and end up with the same spacing.
• Import/export performance improvement - After a sharp decrease in performance in import/export functions, these processes have now returned to acceptable speeds.
• Toggling bookmark no longer affects progress - The percentage complete indicator (on the tool card and in the side menu) is no longer affected by the bookmark.
• Add Target and Original Language to Scripture Pane - If the user closes either the target language or the original language in the scripture pane, they can now be added back to the scripture pane display.
• Alignment complete marker maintained in USFM3 export - When an aligned project is exported and then reimported, the “Alignment complete” status is now persisted.
• Enhanced file logs - Improved file logs are now being captured which will help with debugging and user assistance.
• Verse change notification system - This system notifies the user when a change to the text invalidates previously completed work. This system now accurately shows the number of invalidations on the tool cards before the project is opened in a tool.
• Menu filter in the Word Alignment tool - A menu filter similar to the one in the translationWords tool is now available for the Word Alignment tool.
• Projects open to same position as when closed - A bug was fixed so that a tool opens in the same verse or check the user was in when they closed the project or app.

Known Bugs

• Projects reimported into 1.1.2 - If a project is imported into 1.1.2, then exported, then reimported into 1.1.2, many *s are added to the text. This bug is fixed in 1.1.3 if data corruption has not already taken place. Note: This means if a project is imported once into 1.1.2, then opened in 1.1.3, no data corruption problems occur. If the same project has been imported twice into 1.1.2, data corruption has occurred. In this case please contact us at [email protected]. To avoid this from happening, please upgrade all users to 1.1.3 immediately!
• Improper rendering of long translationWords - tW’s that span multiple original language words may render incorrectly. (Track here)
• Slow performance checking for invalidations - After editing a verse, an automated automated verification is performed to see if this edit has invalidated any previous work. In certain circumstances, this process is unacceptably slow. (Track here)

How to Install

The installation files are available on the translationCore v1.1.3 release page.

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

translationCore v1.1.2

translationCore v1.1.2 Release Notes

1.1.2 Release Notes

Release 1.1.2 Overview

This release includes a patch for a data loss bug found in the 1.1 release.

Major New Features

No major new features were included in this release.

Other New Features

Fixing the data loss bug prompted the following fixes:

• Fix data loss bug - Data in the Word Alignment Tool and translationWords Tool are now correctly saved to disk (not just to memory).
• More frequent data saving - Each time the user navigates to a new verse in the Word Alignment Tool or to a new check in the translationWords tool, an internal git commit is made. This captures revision history much more frequently.

Known Bugs

• Performance issues with upload and download - The time it takes to complete these processes has increased, in some cases, greatly. (Track here.)
• Performance issues with project loading - (Track here.)
• Intermittent upload problems - Inconsistent failure to upload projects to Door43. (Track here.)

1.1 Release Notes

Release 1.1 Overview

Expanding the scope of the existing tools was the theme of this release. Both of the tools in translationCore were significantly expanded in scope as well as a number of smaller enhancements. The result is that the New Testament can now be checked with all the translationWords and the whole Bible can be aligned.

Major New Features

Two new major features are now available:

• Support for “Other Terms” and “Names” in translationWords tool - Up until this release, only part of translationWords (the “Key Terms”) were being displayed for checking. This feature adds in the remaining two categories. Now all of the translationWords can be checked for the New Testament.
• Support for loading and aligning the Old Testament - Aligned Gateway Language texts (including English) is a requirement before checking can be supported. The next step in getting full Bible checking is providing support for Old Testament alignment. A user may now import an Old Testament book and open it in the Word Alignment Tool and align it to the unfoldingWord Hebrew Bible.

Other New Features

• Full USFM3 compatibility - USFM3 markers are preserved through the import and export processes.
• Tool card enhancements - In conjunction with expanding the translationWords tool, the tool card now allows a user to select one or more of the translationWords sections. The percentage complete and invalidated checks counter was updated to reflect only what was selected.
• Hebrew lexicon support - In conjunction with aligning the Old Testament, a full Hebrew lexicon was added.
• WordMAP: lemma fallback - WordMAP is the engine that records Alignment Memory. Prior to this feature, only exact spelling and accent matches were provided as alignment suggestions. With this feature, WordMAP now first checks for an exact spelling and accent match. If this fails, then WordMAP will “fall back” to the lemma (basically the dictionary form of the word) and see if there is any matches based on the lemma. This greatly enhances the effectiveness of the engine.
• Git now bundled with tC - Some (especially Mac) users had problems with messages being displayed that Git needed to be reinstalled, especially after an operating system upgrade. This feature resolves this problem.
• Invalidated checks counter on tool card - When editing a verse, previous work runs the risk of being invalidated in the same tool or in other tools. This feature now gives a counter on the tool card of how many invalidated checks (or for the Word Alignment Tool, verses alignments) have been invalidated.
• Various bug fixes - A number of bug fixes and performance enhancements were successfully performed.
  • CSV export data fixed/improved - Numerous fields in the CSV export were blank, incorrect, or misleading. Multiple fixes were made to make this data helpful and accurate.
  • Projects with numbers now export correctly - Projects with numbers were not exporting correctly (e.g. “430” in Galatians 3:17). These projects now export as expected.

You may also see the full Changelog here.

Known bugs

There are a number of known bugs in this release:

• Memory leak - Though this problem has been greatly improved since the 1.0 release, it is still a problem. After extensive aligning, editing, and realigning, computer memory usage gradually increases until tC finally becomes unresponsive. Exiting and restarting tC after making a few dozen edit/alignments is recommended. (Track here.)
• Inadvertent reset alignments warnings - tC will inadvertently warn users of changes that have caused alignments to be reset when in fact nothing has been reset. (Track here.)
• Greek being shown instead of Gateway Language - When the Gateway Language is removed from the Scripture Pane, Greek is incorrectly being shown in the translationWords check card. (Track here.)
• Projects sometimes do not open to the last used location - Projects may open to the beginning of a project. (Track here.)

Product Overview

The 1.1 release added some much-desired breadth of scope. Here is a brief overview of what translationCore can do.

• General functions
  • User management - Log in with Door43 credentials or continue as Guest
  • Data management - All actions performed on the text are captured in the project’s metadata
  • Project local import/export - Move projects from your file system to translationCore and back
  • Project upload/download from Door43 - Move projects from Door43 to translationCore and back
  • Project re-import - Re-import a project with updated text without losing the existing alignments and checking data
  • Export all checking data to CSV - Access all checking, edit, comment, and bookmark data
  • Support for USFM2 and USFM3 - Import and export projects using industry-standard format
  • Localized user interface - App can be localized into any language (see below)
  • Dynamic source content update - Update source content from Door43 Catalog
  • Check for software update - Check to see if current version of app is up to date
• translationWords tool
  • Gateway Languages support - The source text and all translation helps can be changed to the Gateway Language the speaker knows best.
    • Note: The code for this is complete and in tC, but for this to be beneficial to the user, there must be translated and aligned content. Content teams are working in many Gateway Languages to complete the necessary content. As more source content is made available via the Door43 Catalog, it may be updated in translationCore via “Source Content Update”. This release contains the source content to check the full New Testament from English and check Titus from Hindi.
    • Example: The Portuguese content team completes translating translationWords and 1 John. They also align 1 John to the Greek. They then publish this to the Door43 Catalog. A translationCore user does a “Source Content Update” and downloads Portuguese. Since all the dependencies for translationWords have been met, the app will now add the option able to check 1 John from Portuguese.
  • Full New Testament support - Check any book of the New Testament
  • Full translationWords support - Check your “key terms,” “other terms,” and “names”
  • Pre-identified “checklist” for all key theological terms - Ensure nothing is accidently skipped by working through the pre-identified list
  • View parallel translations* - Reference original language and gateway language resources alongside the target translation
  • Highlighted translation of check in aligned parallel translation - All aligned Gateway translations are pre-highlighted to show how the current check was translated.
  • Select your translation for all key theological terms - Select how the word being checked was translated
  • Just-in-time learning - Read the translationWords, and translationAcademy articles to better understand the concept and how to translate it
  • Verse edit* - If the translation can be improved, the user may edit the translation for the verse
  • Comment - The user may leave a free-form comment on the check
  • Bookmark your check - The user may bookmark any check for future reference
  • Filter checks - The list of checks may be filtered to help the user find what they are looking for
  • Invalidated checks support* - If a verse is edited in such a way that it changes what has already been selected in a different check, the user is notified that the check has been invalidated and they must redo that work
  • Original language lexicon* - A basic original language lexicon is available
• Word Alignment tool
  • New and Old Testament support - align any book of the Bible to the original Greek, Hebrew, or Aramaic
  • Drag and drop alignment - Users may drag the words of their translation from a word list and drop it on the original language word(s) to which it correlates
  • Various alignment pairing options - One-to-one, one-to-many, many-to-one, and many-to-many pairings are all supported
  • Alignment memory suggestions - Each translation/original pairing is saved so that if this pairing comes up in a future verse, the pairing is suggested

*also in Word Alignment tool

translationCore is fr...

translationCore v1.1.0

Note: Do not use this release because it has a serious problem, use v1.1.2 instead!

translationCore v1.1 Release Notes

1.1 Release Notes

Release 1.1 Overview

Expanding the scope of the existing tools was the theme of this release. Both of the tools in translationCore were significantly expanded in scope as well as a number of smaller enhancements. The result is that the New Testament can now be checked with all the translationWords and the whole Bible can be aligned.

Major New Features

Two new major features are now available:

• Support for “Other Terms” and “Names” in translationWords tool - Up until this release, only part of translationWords (the “Key Terms”) were being displayed for checking. This feature adds in the remaining two categories. Now all of the translationWords can be checked for the New Testament.
• Support for loading and aligning the Old Testament - Aligned Gateway Language texts (including English) is a requirement before checking can be supported. The next step in getting full Bible checking is providing support for Old Testament alignment. A user may now import an Old Testament book and open it in the Word Alignment Tool and align it to the unfoldingWord Hebrew Bible.

Other New Features

• Full USFM3 compatibility - USFM3 markers are preserved through the import and export processes.
• Tool card enhancements - In conjunction with expanding the translationWords tool, the tool card now allows a user to select one or more of the translationWords sections. The percentage complete and invalidated checks counter was updated to reflect only what was selected.
• Hebrew lexicon support - In conjunction with aligning the Old Testament, a full Hebrew lexicon was added.
• WordMAP: lemma fallback - WordMAP is the engine that records Alignment Memory. Prior to this feature, only exact spelling and accent matches were provided as alignment suggestions. With this feature, WordMAP now first checks for an exact spelling and accent match. If this fails, then WordMAP will “fall back” to the lemma (basically the dictionary form of the word) and see if there is any matches based on the lemma. This greatly enhances the effectiveness of the engine.
• Git now bundled with tC - Some (especially Mac) users had problems with messages being displayed that Git needed to be reinstalled, especially after an operating system upgrade. This feature resolves this problem.
• Invalidated checks counter on tool card - When editing a verse, previous work runs the risk of being invalidated in the same tool or in other tools. This feature now gives a counter on the tool card of how many invalidated checks (or for the Word Alignment Tool, verses alignments) have been invalidated.
• Various bug fixes - A number of bug fixes and performance enhancements were successfully performed.
  • CSV export data fixed/improved - Numerous fields in the CSV export were blank, incorrect, or misleading. Multiple fixes were made to make this data helpful and accurate.
  • Projects with numbers now export correctly - Projects with numbers were not exporting correctly (e.g. “430” in Galatians 3:17). These projects now export as expected.

You may also see the full Changelog here.

Known bugs

There are a number of known bugs in this release:

• Memory leak - Though this problem has been greatly improved since the 1.0 release, it is still a problem. After extensive aligning, editing, and realigning, computer memory usage gradually increases until tC finally becomes unresponsive. Exiting and restarting tC after making a few dozen edit/alignments is recommended. (Track here.)
• Inadvertent reset alignments warnings - tC will inadvertently warn users of changes that have caused alignments to be reset when in fact nothing has been reset. (Track here.)
• Greek being shown instead of Gateway Language - When the Gateway Language is removed from the Scripture Pane, Greek is incorrectly being shown in the translationWords check card. (Track here.)
• Projects sometimes do not open to the last used location - Projects may open to the beginning of a project. (Track here.)

Product Overview

The 1.1 release added some much-desired breadth of scope. Here is a brief overview of what translationCore can do.

• General functions
  • User management - Log in with Door43 credentials or continue as Guest
  • Data management - All actions performed on the text are captured in the project’s metadata
  • Project local import/export - Move projects from your file system to translationCore and back
  • Project upload/download from Door43 - Move projects from Door43 to translationCore and back
  • Project re-import - Re-import a project with updated text without losing the existing alignments and checking data
  • Export all checking data to CSV - Access all checking, edit, comment, and bookmark data
  • Support for USFM2 and USFM3 - Import and export projects using industry-standard format
  • Localized user interface - App can be localized into any language (see below)
  • Dynamic source content update - Update source content from Door43 Catalog
  • Check for software update - Check to see if current version of app is up to date
• translationWords tool
  • Gateway Languages support - The source text and all translation helps can be changed to the Gateway Language the speaker knows best.
    • Note: The code for this is complete and in tC, but for this to be beneficial to the user, there must be translated and aligned content. Content teams are working in many Gateway Languages to complete the necessary content. As more source content is made available via the Door43 Catalog, it may be updated in translationCore via “Source Content Update”. This release contains the source content to check the full New Testament from English and check Titus from Hindi.
    • Example: The Portuguese content team completes translating translationWords and 1 John. They also align 1 John to the Greek. They then publish this to the Door43 Catalog. A translationCore user does a “Source Content Update” and downloads Portuguese. Since all the dependencies for translationWords have been met, the app will now add the option able to check 1 John from Portuguese.
  • Full New Testament support - Check any book of the New Testament
  • Full translationWords support - Check your “key terms,” “other terms,” and “names”
  • Pre-identified “checklist” for all key theological terms - Ensure nothing is accidently skipped by working through the pre-identified list
  • View parallel translations* - Reference original language and gateway language resources alongside the target translation
  • Highlighted translation of check in aligned parallel translation - All aligned Gateway translations are pre-highlighted to show how the current check was translated.
  • Select your translation for all key theological terms - Select how the word being checked was translated
  • Just-in-time learning - Read the translationWords, and translationAcademy articles to better understand the concept and how to translate it
  • Verse edit* - If the translation can be improved, the user may edit the translation for the verse
  • Comment - The user may leave a free-form comment on the check
  • Bookmark your check - The user may bookmark any check for future reference
  • Filter checks - The list of checks may be filtered to help the user find what they are looking for
  • Invalidated checks support* - If a verse is edited in such a way that it changes what has already been selected in a different check, the user is notified that the check has been invalidated and they must redo that work
  • Original language lexicon* - A basic original language lexicon is available
• Word Alignment tool
  • New and Old Testament support - align any book of the Bible to the original Greek, Hebrew, or Aramaic
  • Drag and drop alignment - Users may drag the words of their translation from a word list and drop it on the original language word(s) to which it correlates
  • Various alignment pairing options - One-to-one, one-to-many, many-to-one, and many-to-many pairings are all supported
  • Alignment memory suggestions - Each translation/original pairing is saved so that if this pairing comes up in a future verse, the pairing is suggested

*also in Word Alignment tool

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.  

The Road Ahead

translationCore is a program that is highly dependent on content. All of the checks are built on content (e.g. translationWords) and are dependent an aligned Gateway Language book of the Bible before the checks can be displayed.

The 1.1 release removes the last major obstacle for starting the alignment process for the Old Testament. The next major milestone is a technical one - adding support for any unlocked book of the Bible. Currently, this is true for all the New Testament. Soon, it will be the case for the whole Bible. The next milestone is adding the translationNotes tool - a new tool that focuses on semantic, cultural, genre, and grammatical checks. After this, a n...

translationCore v1.0.2

translationCore 1.0.2 Release Notes

1.0.2 Release Notes

Release 1.0.2 Overview

Bug fixes was the theme of this release! No major new features were added, but enhanced tokenization, performance enhancements, better USFM handling, and a lot of bug fixes have been included in this release.

Major New Features

No major new features in this release.

Other New Features

• Enhancements to the tokenizer for Hindi use case - The tokenizer was incorrectly splitting some Hindi words. The tokenizer is now working properly for Hindi.

• Enhanced USFM support - Significant work was performed to improve translationCore’s handling of USFM tags. This includes correctly displaying USFM, not displaying USFM tags (except in edit mode), and improved import and export of USFM projects so tags and whitespace are preserved. Note: though handling of USFM is significantly improved, the immensity of this feature has precluded comprehensive QA testing before the 1.0.2 release.

• Full morphological data - When a user clicks on a Greek word, morphological data now shows up as words (e.g. “Noun, Accusative, Feminine, Singular”), not as a group of letters and commas.

• Option to not show “Invalidated” warning - A checkbox is now available on the “Invalidated” warning so that the user won’t see the warning again. This resets when the app is restarted or the user logs out.

• List of languages updated with every release - The list of available language codes and names (from translationDatabase) is now updated for each release.

• Performance enhancements - numerous performance enhancements are included in this release

  • Project loading - The time it takes to load a project has been greatly improved.

  • Tool loading - The time it takes to load a tool has been greatly improved.

  • Improved scrolling - The side menu doesn’t jump around in the Word Alignment and translationWords tools.

  • Navigation - The time it takes to navigate between checks/verses in the side menu has been greatly improved.

  • Memory leak - There was a memory leak in tC that caused it to consume more and more memory until it appeared to hang. This has been improved about 5x, but is not yet fully addressed (see “Known bugs”).

• New App Localizations - The app can now be localized to Brazilian Portuguese and Spanish. (Note: this is not full Gateway Language support where the user can check from those languages, but rather all the buttons, menus, instructions, and warnings can be displayed in those languages.) See “We Need Your Help” to see how you can localize tC to your language!

• Various bug fixes - A number of bug fixes and performance enhancements were successfully performed.

  • Reimported projects now update verse edits log - Now a complete “change log” is preserved in the CSV export. (Note that edits performed outside of tC will incorrectly indicate that they were edited in the Word Alignment tool. The other information about the edits is correct.)

  • Attempted imports of USFM3 projects from Door43 now blocked - rather than importing a blank project, these projects are now being blocked from importing.

  • Warning again issued for 0.7 (or earlier) projects - These unsupported projects again throw a warning that they are not supported.

  • Progress indicator on Word Alignment tool card fixed - Instead of always reading “0% Complete” it now tracks progress.

  • Improved selecting of special characters - Improvements were made in translationWords so that selections containing special characters are now handled properly.

  • “Software Update” now works for Win64 - The correct file is now downloaded and installed for Windows 64bit users.

You may also see the full Changelog here.

Known bugs

There are a number of known bugs in this release:

• Memory leak - Though this problem has been greatly improved (~5x better than it was), it is still a problem. After extensive aligning, editing, and realigning, computer memory usage gradually increases until tC finally becomes unresponsive. Exiting and restarting tC after making a few dozen edit/alignments is recommended. (Track here.)

• Inadvertent reset alignments warnings - tC will inadvertently warn users of changes that have caused alignments to be reset when in fact nothing has been reset. (Track here.)

• Missing data in the CSV export for verse edits: The groupId, groupName, occurrence, and quote columns are all blank in the VerseEdits CSV export file. (Track here.)

Product Overview

The major functionality of translationCore has not changed since 1.0. Here is a brief overview of what translationCore can do.

• General functions

  • User management - Log in with Door43 credentials or continue as Guest

  • Data management - All actions performed on the text are captured in the project’s metadata

  • Project local import/export - Move projects from your file system to translationCore and back

  • Project upload/download from Door43 - Move projects from Door43 to translationCore and back

  • Project re-import - Re-import a project with updated text without losing the existing alignments and checking data

  • Export all checking data to CSV - Access all checking, edit, comment, and bookmark data

  • Support for USFM2 and USFM3 - Import and export projects using industry-standard format

  • Localized user interface - App can be localized into any language (see below)

  • Dynamic source content update - Update source content from Door43 Catalog

  • Check for software update - Check to see if current version of app is up to date

• translationWords tool

  • Gateway Languages support - The source text and all translation helps can be changed to the Gateway Language the speaker knows best.

    • Note: The code for this is complete and in tC, but for this to be beneficial to the user, there must be translated and aligned content. Content teams are working in many Gateway Languages to complete the necessary content. As more source content is made available via the Door43 Catalog, it may be updated in translationCore via “Source Content Update”. This release contains the source content to check the full New Testament from English and check Titus from Hindi.

    • Example: The Portuguese content team completes translating translationWords and 1 John. They also align 1 John to the Greek. They then publish this to the Door43 Catalog. A translationCore user does a “Source Content Update” and downloads Portuguese. Since all the dependencies for translationWords have been met, the app will now add the option able to check 1 John from Portuguese.

  • Full New Testament support* - Check any book of the New Testament

  • Pre-identified “checklist” for all key theological terms - Ensure nothing is accidently skipped by working through the pre-identified list

  • View parallel translations* - Reference original language and gateway language resources alongside the target translation

  • Highlighted translation of check in aligned parallel translation - All aligned Gateway translations are pre-highlighted to show how the current check was translated.

  • Select your translation for all key theological terms - Select how the word being checked was translated

  • Just-in-time learning - Read the translationWords, and translationAcademy articles to better understand the concept and how to translate it

  • Verse edit* - If the translation can be improved, the user may edit the translation for the verse

  • Comment - The user may leave a free-form comment on the check

  • Bookmark your check - The user may bookmark any check for future reference

  • Filter checks - The list of checks may be filtered to help the user find what they are looking for

  • Invalidated checks support* - If a verse is edited in such a way that it changes what has already been selected in a different check, the user is notified that the check has been invalidated and they must redo that work

  • Original language lexicon* - A basic original language lexicon is available

• Word Alignment tool

  • Drag and drop alignment - Users may drag the words of their translation from a word list and drop it on the original language word(s) to which it correlates

  • Various alignment pairing options - One-to-one, one-to-many, many-to-one, and many-to-many pairings are all supported

  • Alignment memory suggestions - Each translation/original pairing is saved so that if this pairing comes up in a future verse, the pairing is suggested

*also in Word Alignment tool

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.

The Road Ahead

Now that translationCore has full New Testament support, continued development will turn next to expanding the Word A...

translationCore v1.0.0

translationCore v1.0 Release Notes

1.0 Release Notes

Release 1.0 Overview

With this release, translationCore now supports checking any book of the New Testament with the translationWords tool. Checking can be completed in any Gateway Language that has the needed lexical and source material for the New Testament. Since Gateway Language translation and alignment work is ongoing and continually updated, translationCore now allows users to check for this new content (or other supplemental translations) whenever they want.

Major New Features

Two new features are available in this release:

• New Testament Support for translationWords - All the key theological terms in any translation for any book of the New Testament may now be checked with this tool. Gateway Language support is fully enabled with this tool but requires translationWords to be translated and at least one New Testament book to be aligned to the Greek.
• Dynamic Source Content Update - Users may now dynamically check for any new or supplemental content that has been published to the Door43 Catalog. As additional Gateway Language resources are added to the Catalog, they may be dynamically imported into translationCore which will "unlock" new books or languages from which to check.

Other New Features

• Select and move multiple words at once - In the Word Alignment tool, a user may now multi-select any number of words from the word bank and move them all at the same time.
• Various bug fixes - A number of bug fixes and performance enhancements were successfully performed.

You may also see the full Changelog here.

Known bugs

There are a number of known bugs in this release:

• Reimported projects do not update verse edits log - This will affect the edit history. (Track here.)
• Blank imports of USFM3 projects from Door43 - Importing USFM3 projects from Door43 is not supported in this release, but if the user tries, the process is completed but produces a blank project. (Track here.)
• No warning issued for 0.7 (or earlier) projects - Projects from tC version 0.7 or earlier are no longer supported. For existing projects on a machine being upgraded to 1.0, no warning is displayed when the project is selected, and the app appears to do nothing. (Track here.)
• Poor performance - Though not technically a bug, the time needed to load projects and navigate within the tools (especially on older, slower machines) is longer than desired. (Track here.)
• Inadvertent reset alignments warnings - tC will inadvertently warn users of changes that have caused alignments to be reset when in fact nothing has been reset. (Track here.)
• Progress indicator mistakenly reads 0% - For projects that have been (partially) aligned in the Word Alignment tool, the progress in the indicator on the tool card may read 0%, especially after upgrading the app version. (Track here.)
• Intermittent inability to save selections containing special characters - In some instances, selections containing special characters cannot be saved. (Track here.)

Product Overview

The much-awaited release of translationCore 1.0 is now here! Here is a brief overview of what translationCore can do.

• General functions
  • User management - Log in with Door43 credentials or continue as Guest
  • Data management - All actions performed on the text are captured in the project's metadata
  • Project local import/export - Move projects from your file system to translationCore and back
  • Project upload/download from Door43 - Move projects from Door43 to translationCore and back
  • Project re-import - Re-import a project with updated text without losing the existing alignments and checking data
  • Export all checking data to CSV - Access all checking, edit, comment, and bookmark data
  • Support for USFM2 and USFM3 - Import and export projects using industry-standard format
  • Localized user interface - App can be localized into any language (see below)
  • Dynamic source content update - Update source content from Door43 Catalog
  • Check for software update - Check to see if current version of app is up to date
• translationWords tool
  • Gateway Languages support - The source text and all translation helps can be changed to the Gateway Language the speaker knows best.
    • Note: The code for this is complete and in tC, but for this to be beneficial to the user, there must be translated and aligned content. Content teams are working in many Gateway Languages to complete the necessary content. As more source content is made available via the Door43 Catalog, it may be updated in translationCore via "Source Content Update". This release contains the source content to check the full New Testament from English and check Titus from Hindi.
    • Example: The Portuguese content team completes translating translationWords and 1 John. They also align 1 John to the Greek. They then publish this to the Door43 Catalog. A translationCore user does a "Source Content Update" and downloads Portuguese. Since all the dependencies for translationWords have been met, the app will now add the option to check 1 John from Portuguese.
  • Full New Testament support* - Check any book of the New Testament
  • Pre-identified "checklist" for all key theological terms - Ensure nothing is accidently skipped by working through the pre-identified list
  • View parallel translations* - Reference original language and gateway language resources alongside the target translation
  • Highlighted translation of check in aligned parallel translation - All aligned Gateway translations are pre-highlighted to show how the current check was translated.
  • Select your translation for all key theological terms - Select how the word being checked was translated
  • Just-in-time learning - Read the translationWords, and translationAcademy articles to better understand the concept and how to translate it
  • Verse edit* - If the translation can be improved, the user may edit the translation for the verse
  • Comment - The user may leave a free-form comment on the check
  • Bookmark your check - The user may bookmark any check for future reference
  • Filter checks - The list of checks may be filtered to help the user find what they are looking for
  • Invalidated checks support* - If a verse is edited in such a way that it changes what has already been selected in a different check, the user is notified that the check has been invalidated and they must redo that work
  • Original language lexicon* - A basic original language lexicon is available
• Word Alignment tool
  • Drag and drop alignment - Users may drag the words of their translation from a word list and drop it on the original language word(s) to which it correlates
  • Various alignment pairing options - One-to-one, one-to-many, many-to-one, and many-to-many pairings are all supported
  • Alignment memory suggestions - Each translation/original pairing is saved so that if this pairing comes up in a future verse, the pairing is suggested

*also in Word Alignment tool

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.

The Road Ahead

Now that translationCore has full New Testament support, continued development will turn next to expanding the Word Alignment tool to include Old Testament support. Since checking support requires aligned text, this feature will open the door for the alignment teams to prepare for eventual Old Testament support for checking tools.

After this, the current plan is to add more checking tools. First, translationWords will be expanded beyond just key theological terms to include other important terms and names. Next, a new tool will be created that focuses on semantic, cultural, genre, and grammatical checks. After this, a new platform for checking tools will be created that will allow users to create their own checks and import them into translationCore. Everything will function the same, except the checks being performed will be user-created.

By this point, the content teams should be well on their way to providing the needed content and alignment data required for Old Testament support in all the checking tools.

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".)
• Improved localization - We are using a crowd-sourced platform to localize translationCore. If you notice that some of the translated user interface verbiage can be improved, please update the text for us! You can do this by navigating to [https://crowdin.com/project/translationcore](https://crowdin.c...

translationCore v0.10.1

translationCore v0.10.1 Release Notes

0.10.1 Release Notes

This is a minor release with a of couple bug fixes:

• Bug fix: When in the Word Alignment tool, accessing a verse that exists in the target translation but not in the UGNT will no longer crash the app.

• Bug fix: If a verse exists in the target language but not in the UGNT, tC will now export that project and the “extra” verse to USFM3.

0.10 Release Notes

Release 0.10 Overview

One of the prerequisites for a Gateway Language to be supported in translaionCore (tC) is that it must be aligned to the original languages (e.g. Greek, Hebrew). This release (0.10) is a huge step towards helping make tC more effective for translation aligners. All of the major features and most of the minor features directly improve the ease and efficacy of alignment in tC.

Major New Features

Many new features on the product roadmap were planned for 0.10 and were completed successfully:

• Notification of invalidated work - After a user has made selections in the translationWords (tW) tool or alignments in the Word Alignment (wA) tool, there is the real possibility that these verses are edited, and the completed work rendered invalidated. This feature notifies the user that work has been invalidated and displays a “broken link” icon to identify which verse/check needs to be revisited.

• Side menu filter - In the tW tool, a filter has been added to the side menu so that a user may only display checks/verses that have a certain attribute (e.g. “Invalidated”, “Bookmarks”, “Selected”, “No Selection”, “Verse edit”, or “Comments”).

• Improvements to wA tool -

  • “Alignment Complete” toggle - If all the original language words have been aligned to something and all the target language words have been used, then this will toggle on automatically. This toggle allows the user to manually override this requirement and obtain the green checkmark even though there are unaligned words.

  • Complete refactor of wA tool - This future-facing code restructuring better positions to tool for future development.

  • Performance optimization - For a longer New Testament book, tC would grind to a virtual standstill. After optimization, operations that took 40+ seconds are taking about 1 second.

• Integrating Basic WordMAP into the wA tool - This feature records previous alignments for the current project and suggests these alignments when the user clicks “Refresh” or navigates to a different verse. Suggestions for a verse can be accepted or rejected individually or in whole.

• Reimport existing USFM project - If a user updates the text of a project outside of their instance of tC, they can now reimport the USFM project over an existing tC project. This will update the text, but all selections, edits, and comments will remain. Any work invalidated by the external edits will be flagged as “invalidated”.

Other New Features

• Partial invalidation - When changes to the text occur, the wA tool now only resets the minimum number of aligned words, instead of resetting the entire verse.

• Tool loading optimization - Once a tool was selected, launching the app was very slow, especially for a slow computer. This process was optimized with loading now taking around 1/10 the time.

• Standardized naming of projects - Projects imported into tC will now be renamed to follow the Door43 naming spec. The application now requires the user to give the project a 3 or 4 alpha character Translation Identifier. The optional “Project Nickname” field was also added so the user can use their own naming system. The Project Nickname can be displayed by hovering over the project’s name in the stepper and menu bars.

• Multiple versions of same book for same language - With the addition of the “Translation Identifier” field, any number of translations may now be added for the same book/language combination.

• Partial refactor of tC Core & tW tool - This future-facing code restructuring better positions the app for future development and ease of bug identification and fixes.

You may also see the full Changelog here.

Known bugs

There are a number of known bugs in this release:

• Incorrect warning when loading 0.9 project - For projects from tC ver. 0.9/0.9.1, the first time they are opened in 0.10 an incorrect warning pops up temporarily that states “A project with this identifier already exists for this language and book.” (Track here.)

• Reimported projects do not update verse edits log - This will affect the edit history. (Track here.)

• WordMAP suggests blank alignments - In several instances, WordMAP incorrectly suggests a blank alignment. (Track here and here.)

• Case sensitive/insensitive issue for “Translation Identifier” field - Importing a project with “ult” as the “Translation Identifier” and then again with “ULT” will result in an unexpected “This project already exists” warning. (Track here.)

• Duplicate pop-overs for “Invalidated” items in menu - (Track here.)

• Fully aligned verses not marked as complete - Alignments completed in a previous version of tC will all still be marked as incomplete, even if all target and original language words have been aligned. The Alignment Complete switch can manually be set to On. (Track here.)

• Blank imports of USFM3 projects from Door43 - Importing USFM3 projects from Door43 is not supported, but if the user tries, the process is completed but produces a blank project. (Track here.)

• Green check displayed for checks with no selection - In some instances, a green checkmark will appear in the side menu for checks in the tW tool that have no selection. (Track here.)

Product Overview

translationCore is steadily marching towards a 1.0 release which will feature support for checking in the translationWords tool for the entire New Testament, using any Gateway Language.

Though still in a Beta version that only supports checking in one tool (translationWords) for one book of the Bible (Titus), the user can now check their project from either English or Hindi -- the only thing preventing more Gateway Languages from being supported is the translated and aligned content for those languages!

To assist in the aligning of the Bible, translationCore also has the Word Alignment tool which now allows users to align any book of the New Testament to the unfoldingWord Greek New Testament (UGNT). This is a prerequisite for “unlocking” checking for a new book of the Bible.

The Road Ahead

The next step for translationCore is for the 1.0 release which will feature full New Testament support for checking in the translationWords tool! It will also allow users to dynamically update their source content, instead of waiting for that content to be bundled with the next release of tC.

After the 1.0 release, development efforts will focus on expanding the Word Alignment tool to support alignment in the Old Testament. At the same time, more translation checking tools will be added for the New Testament.

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

• Improved localization - We are using a crowd-sourced platform to localize translationCore. If you notice that some of the translated user interface can be improved, please update the text for us! You can do this by navigating to https://crowdin.com/project/translationcore, creating a user profile, finding the correct word or phrase that needs to be improved, and suggesting a change! (Note: these changes will not be incorporated until the next release of tC.)

How to Install

The installation files are available on the translationCore v0.10.1 release page.

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 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 and the executable should automatically download.

  • If your download hasn't started, click...

translationCore v0.10.0

translationCore v0.10 Release Notes

0.10 Release Notes

Release 0.10 Overview

One of the prerequisites for a Gateway Language to be supported in translaionCore (tC) is that it must be aligned to the original languages (e.g. Greek, Hebrew). This release (0.10) is a huge step towards helping make tC more effective for translation aligners. All of the major features and most of the minor features directly improve the ease and efficacy of alignment in tC.

Major New Features

Many new features on the product roadmap were planned for 0.10 and were completed successfully:

• Notification of invalidated work - After a user has made selections in the translationWords (tW) tool or alignments in the Word Alignment (wA) tool, there is the real possibility that these verses are edited, and the completed work rendered invalidated. This feature notifies the user that work has been invalidated and displays a “broken link” icon to identify which verse/check needs to be revisited.

• Side menu filter - In the tW tool, a filter has been added to the side menu so that a user may only display checks/verses that have a certain attribute (e.g. “Invalidated”, “Bookmarks”, “Selected”, “No Selection”, “Verse edit”, or “Comments”).

• Improvements to wA tool -

  • “Alignment Complete” toggle - If all the original language words have been aligned to something and all the target language words have been used, then this will toggle on automatically. This toggle allows the user to manually override this requirement and obtain the green checkmark even though there are unaligned words.

  • Complete refactor of wA tool - This future-facing code restructuring better positions to tool for future development.

  • Performance optimization - For a longer New Testament book, tC would grind to a virtual standstill. After optimization, operations that took 40+ seconds are taking about 1 second.

• Integrating Basic WordMAP into the wA tool - This feature records previous alignments for the current project and suggests these alignments when the user clicks “Refresh” or navigates to a different verse. Suggestions for a verse can be accepted or rejected individually or in whole.

• Reimport existing USFM project - If a user updates the text of a project outside of their instance of tC, they can now reimport the USFM project over an existing tC project. This will update the text, but all selections, edits, and comments will remain. Any work invalidated by the external edits will be flagged as “invalidated”.

Other New Features

• Partial invalidation - When changes to the text occur, the wA tool now only resets the minimum number of aligned words, instead of resetting the entire verse.

• Tool loading optimization - Once a tool was selected, launching the app was very slow, especially for a slow computer. This process was optimized with loading now taking around 1/10 the time.

• Standardized naming of projects - Projects imported into tC will now be renamed to follow the Door43 naming spec. The application now requires the user to give the project a 3 or 4 alpha character Translation Identifier. The optional “Project Nickname” field was also added so the user can use their own naming system. The Project Nickname can be displayed by hovering over the project’s name in the stepper and menu bars.

• Multiple versions of same book for same language - With the addition of the “Translation Identifier” field, any number of translations may now be added for the same book/language combination.

• Partial refactor of tC Core & tW tool - This future-facing code restructuring better positions the app for future development and ease of bug identification and fixes.

You may also see the full Changelog here.

Known bugs

There are a number of known bugs in this release:

• Incorrect warning when loading 0.9 project - For projects from tC ver. 0.9/0.9.1, the first time they are opened in 0.10 an incorrect warning pops up temporarily that states “A project with this identifier already exists for this language and book.” (Track here.)

• Reimported projects do not update verse edits log - This will affect the edit history. (Track here.)

• WordMAP suggests blank alignments - In several instances, WordMAP incorrectly suggests a blank alignment. (Track here and here.)

• Case sensitive/insensitive issue for “Translation Identifier” field - Importing a project with “ult” as the “Translation Identifier” and then again with “ULT” will result in an unexpected “This project already exists” warning. (Track here.)

• Duplicate pop-overs for “Invalidated” items in menu - (Track here.)

• Fully aligned verses not marked as complete - Alignments completed in a previous version of tC will all still be marked as incomplete, even if all target and original language words have been aligned. The Alignment Complete switch can manually be set to On. (Track here.)

• Blank imports of USFM3 projects from Door43 - Importing USFM3 projects from Door43 is not supported, but if the user tries, the process is completed but produces a blank project. (Track here.)

• Green check displayed for checks with no selection - In some instances, a green checkmark will appear in the side menu for checks in the tW tool that have no selection. (Track here.)

Product Overview

translationCore is steadily marching towards a 1.0 release which will feature support for checking in the translationWords tool for the entire New Testament, using any Gateway Language.

Though still in a Beta version that only supports checking in one tool (translationWords) for one book of the Bible (Titus), the user can now check their project from either English or Hindi -- the only thing preventing more Gateway Languages from being supported is the translated and aligned content for those languages!

To assist in the aligning of the Bible, translationCore also has the Word Alignment tool which now allows users to align any book of the New Testament to the unfoldingWord Greek New Testament (UGNT). This is a prerequisite for “unlocking” checking for a new book of the Bible.

The Road Ahead

The next step for translationCore is for the 1.0 release which will feature full New Testament support for checking in the translationWords tool! It will also allow users to dynamically update their source content, instead of waiting for that content to be bundled with the next release of tC.

After the 1.0 release, development efforts will focus on expanding the Word Alignment tool to support alignment in the Old Testament. At the same time, more translation checking tools will be added for the New Testament.

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

• Improved localization - We are using a crowd-sourced platform to localize translationCore. If you notice that some of the translated user interface can be improved, please update the text for us! You can do this by navigating to https://crowdin.com/project/translationcore, creating a user profile, finding the correct word or phrase that needs to be improved, and suggesting a change! (Note: these changes will not be incorporated until the next release of tC.)

How to Install

The installation files are available on the translationCore v0.10.0 release page.

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

translationCore v0.9.1

0.9.1 Release Notes

This is a minor release with a of couple bug fixes:

• Bug fix: Door43 tS projects that have no tC checking data can again be imported.
• Content update: The alignment data for the Titus 1:15 (ULT) was updated.

0.9.0 Release Notes

Major New Features

One new feature on the product roadmap was planned for 0.9.0 and was completed successfully:

• Check from a Gateway Language other than English - The book of Titus can now be checked either from English or from Hindi. The infrastructure is now in place to support any other Gateway Language. (Selecting a Gateway Language from which to check can be done from the translationWords tool card on the tools page.)

Two new features on the product roadmap that were originally planned for a future release of tC were also completed successfully in 0.9.0:

• App localization - The application itself (menus, instructions, alerts, etc.) can be displayed in either English or Hindi. The infrastructure is now in place to support any other language. (Changing the app’s locale can be accessed via the “Actions” menu.)
• Edit verse not being checked - A user can now edit any verse in their project. This feature is available in both translationWords tool and the Word Alignment tool. (This feature can be accessed through the expanded Scripture Pane - click on the “four-arrow expand” button in the Scripture Pane, then click on the “pencil” of the verse you desire to edit.)

Other New Features

• Highlighting in the Scripture Pane - in the translationWords tool, checks are now pegged to the Greek. This allows for automatic highlighting of any Gateway Language text that has been aligned to the Greek (literal or dynamic texts). Also, when the check for a target language is selected, that selection now also appears in the Scripture Pane.
• Word Alignment tool improvements -
  • Placekeepers are kept in wordlist when words are aligned
  • Occurrence numbers on target language words
  • Improved User Interface layout & handling
  • Support for opening any New Testament Book in Word Alignment tool
    *User Feedback - Users may now submit feedback directly from tC. (This feature can be can be accessed via the “Actions” menu.)
• Check for software updates - Due to security concerns, tC does not check for software updates without being prompted, but the user may now prompt the app to look for updates. (This feature can be can be accessed via the “Actions” menu.)
• Improved USFM 2 Import & Export - Better support now available, with projects from earlier versions of translationStudio now supported.
• USFM 3 Import & Export - Support for alignment data saved as USFM3 now supported both for import & export.
• Complete refactor of the build process - With every successful pull request, a new build is created (though not recommended for public use!).

Breaking Changes

Due to the pivot from checking data being based on the English to checking data being based on the Original Languages, any check data that has been made in previous versions of translationCore will not be accessible in 0.9.0 or beyond. We are sincerely sorry for this inconvenience.

You may also see the full Changelog here.

Product Overview

translationCore is steadily marching towards a 1.0 release which will feature support for checking the entire New Testament, using any Gateway Language.

This release (0.9.0) is a huge step towards that goal. Though still in a Beta version that only supports checking in one tool (translationWords) for one book of the Bible (Titus), the user can now check their project from either English or Hindi -- the only thing preventing more Gateway Languages from being supported is the translated and aligned content for those languages!

To assist in the aligning of the Bible, translationCore also has the Word Alignment tool which now allows users to align any book of the New Testament to the unfoldingWord Greek New Testament (UGNT). This is a prerequisite for “unlocking” checking for a new book of the Bible.

The Road Ahead

Since translationCore both consumes alignment data and assists in the production of alignment data, there is a little bit of a chicken and egg scenario. To help pave the way for faster alignment, the next phase of development will primarily focus on improving the usability and efficiency of the Word Alignment tool, as well as adding support for aligning the Old Testament.

After this, translationCore software development will shift to the translationWords tool - focusing on improving workflow, usability, and complete support for the New Testament.

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”.)
• Improved localization - We are using a crowd-sourced platform to localize translationCore. If you notice that some of the translated user interface can be improved, please update the text for us! You can do this by navigating to https://crowdin.com/project/translationcore, creating a user profile, finding the correct word or phrase that needs to be improved, and suggesting a change! (Note: these changes will not be incorporated until the next release of tC.)

How to Install

See the attached installation files above.

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

translationCore v0.9.0

Release Notes

Major New Features

One new feature on the product roadmap was planned for 0.9.0 and was completed successfully:

• Check from a Gateway Language other than English - The book of Titus can now be checked either from English or from Hindi. The infrastructure is now in place to support any other Gateway Language. (Selecting a Gateway Language from which to check can be done from the translationWords tool card on the tools page.)

Two new features on the product roadmap that were originally planned for a future release of tC were also completed successfully in 0.9.0:

• App localization - The application itself (menus, instructions, alerts, etc.) can be displayed in either English or Hindi. The infrastructure is now in place to support any other language. (Changing the app’s locale can be accessed via the “Actions” menu.)
• Edit verse not being checked - A user can now edit any verse in their project. This feature is available in both translationWords tool and the Word Alignment tool. (This feature can be accessed through the expanded Scripture Pane - click on the “four-arrow expand” button in the Scripture Pane, then click on the “pencil” of the verse you desire to edit.)

Other New Features

• Highlighting in the Scripture Pane - in the translationWords tool, checks are now pegged to the Greek. This allows for automatic highlighting of any Gateway Language text that has been aligned to the Greek (literal or dynamic texts). Also, when the check for a target language is selected, that selection now also appears in the Scripture Pane.
• Word Alignment tool improvements -
  • Placekeepers are kept in wordlist when words are aligned
  • Occurrence numbers on target language words
  • Improved User Interface layout & handling
  • Support for opening any New Testament Book in Word Alignment tool
    *User Feedback - Users may now submit feedback directly from tC. (This feature can be can be accessed via the “Actions” menu.)
• Check for software updates - Due to security concerns, tC does not check for software updates without being prompted, but the user may now prompt the app to look for updates. (This feature can be can be accessed via the “Actions” menu.)
• Improved USFM 2 Import & Export - Better support now available, with projects from earlier versions of translationStudio now supported.
• USFM 3 Import & Export - Support for alignment data saved as USFM3 now supported both for import & export.
• Complete refactor of the build process - With every successful pull request, a new build is created (though not recommended for public use!).

Breaking Changes

Due to the pivot from checking data being based on the English to checking data being based on the Original Languages, any check data that has been made in previous versions of translationCore will not be accessible in 0.9.0 or beyond. We are sincerely sorry for this inconvenience.

You may also see the full Changelog here.

Product Overview

translationCore is steadily marching towards a 1.0 release which will feature support for checking the entire New Testament, using any Gateway Language.

This release (0.9.0) is a huge step towards that goal. Though still in a Beta version that only supports checking in one tool (translationWords) for one book of the Bible (Titus), the user can now check their project from either English or Hindi -- the only thing preventing more Gateway Languages from being supported is the translated and aligned content for those languages!

To assist in the aligning of the Bible, translationCore also has the Word Alignment tool which now allows users to align any book of the New Testament to the unfoldingWord Greek New Testament (UGNT). This is a prerequisite for “unlocking” checking for a new book of the Bible.

The Road Ahead

Since translationCore both consumes alignment data and assists in the production of alignment data, there is a little bit of a chicken and egg scenario. To help pave the way for faster alignment, the next phase of development will primarily focus on improving the usability and efficiency of the Word Alignment tool, as well as adding support for aligning the Old Testament.

After this, translationCore software development will shift to the translationWords tool - focusing on improving workflow, usability, and complete support for the New Testament.

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”.)
• Improved localization - We are using a crowd-sourced platform to localize translationCore. If you notice that some of the translated user interface can be improved, please update the text for us! You can do this by navigating to https://crowdin.com/project/translationcore, creating a user profile, finding the correct word or phrase that needs to be improved, and suggesting a change! (Note: these changes will not be incorporated until the next release of tC.)

How to Install

See the attached installation files above.

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