Observe: this text was first posted in December 2016
Adapt It version 6.8.1 release 09 December 2016
Recognized Difficulty in Linux Xenial model 6.8.1 and a very good work-around
Observe to Linux customers: There’s a drawback in the File > Print and Preview features in the Linux Xenial and Yakkety variations that may cause this system to give up unexpectedly. The issue doesn’t affect Windows versions. It additionally doesn’t have an effect on the Linux Exact, Trusty, Vivid, or Wily variations of Adapt It. We’re nonetheless working on a fix for this drawback. At the moment we advocate that you simply export your texts utilizing the Export-Import menu’s “Export Interlinear Text…” perform, open the exported file in LibreOffice or MS Phrase, and preview or print the interlinear show from there. Interlinear paperwork exported from Adapt It are formatted into tables and have an entire set of types. Additionally they have the advantage of being edited before printing.
Function modifications and new features in 6.8.1
This launch options some essential enhancements and bug fixes in relation to Adapt It collaboration with Paratext/Bibledit.
- Adapt It supports collaboration with Paratext 8 on both Home windows and Linux. It is best to upgrade to Adapt It 6.8.1 at the similar time that you simply improve from Paratext 7.x to Paratext Eight. Once Paratext Eight has been installed and Paratext venture knowledge has been migrated from your previous Paratext 7.x venture folder to the brand new Paratext 8 tasks folder, Adapt It 6.8.1 will routinely detect that Paratext Eight has been put in and will routinely look for Paratext tasks in your “My Paratext 8 Projects” folder (Paratext8Projects on Linux). Therefore, so long as you’ve migrated your Paratext 7 knowledge to Paratext 8, Adapt It 6.Eight.1should proceed collaborating with Paratext Eight for all Adapt It tasks that have been beforehand arrange by an administrator to collaborate with Paratext 7.x.
WARNING: When you have been utilizing an Adapt It model prior to six.Eight.zero on Home windows, or previous to 6.8.1 on Linux in collaboration with Paratext 7.x, you’ll need to improve to this version 6.8.1 as a way to continue collaborating with Paratext 8. You also needs to make sure that your Paratext tasks have been migrated to the new “My Paratext 8 Projects” directory (Paratext8Projects on Linux).
- This new version of Adapt It will still work for customers who have tasks set as much as collaborate with Paratext 7.x. Installing Paratext Eight is just not vital to use this model (6.Eight.0) of Adapt It. This version will proceed to collaborate with a consumer’s Paratext 7.x knowledge if Adapt It was previously set up to collaborate with Paratext 7.x.
- When establishing collaboration with Paratext (or Bibledit) utilizing Adapt It’s Setup or Remove Collaboration dialog, the analyzing of the books out there in a specific undertaking proceeds far more shortly now – just some seconds, in comparison with a number of minutes beforehand.
- Extra localization to Indonesian has been accomplished.
- Copying chosen source text to the clipboard. Formerly, there was no straightforward means. Copying selected supply textual content copied the goal textual content underneath the selected supply text. This still occurs, nevertheless, if the ALT key’s held down while clicking the Copy command on the Edit menu, the selected supply text will as an alternative be copied to the clipboard. (Observe: CTRL-C shortcut isn’t supported, by design, in Adapt It – besides within the phrasebox, or the compose bar’s text field. This has been the case for years, and won’t be changed.)
- The document creation code has extra checks to detect defective markup that may lead to an software failure, or a corrupted doc.
- The appliance now exams for certain markup errors, and if it finds one it halts the creation, and provides a warning message to advise the consumer to click a checkbox within the View page of Preferences to have a diagnostic log file produced.
- Manufacturing of a diagnostic logfile is supported. It gets stored within the _LOGS_EMAIL_REPORTS folder inside the Adapt It Unicode Work folder. The file is known as: Log_For_Document_Creation.txt. It is deliberately small, with simply important info: the filename (first line), and then five subsequent strains listing the final five phrases appropriately parsed in from the input supply textual content before the failure occurred. Each such line lists the chapter:verse info the place the failure happened. The dangerous markup will probably be situated within that verse, after the last word listed in this file. The consumer can then look at the supply check in a phrase processor, and probably repair the error himself, then resave the fastened source text, and retry the doc creation once more. Notice: producing the log file is sluggish: about 150 phrases a second are scanned, so a e-book like Luke may take as much as three minutes to get to the failure level. An info message is shown to the consumer informing her or him that the log file is being produced, and to attend. But that only happens within the Windows build. OSX and Linux builds don’t present the knowledge message, however they nonetheless produce the log file. If the log file is empty, then the error was in all probability a utf-Eight encoding error – perhaps some non-utf-8 bytes are somewhere in the supply text. (To fix encoding errors, perhaps greatest to ship the supply text file to one of many builders.)
- The Shift-Launch function (i.e. Launching Adapt It with SHIFT key held down, to bypass one or each configuration information) has been improved. Beforehand, if a undertaking was a collaboration one, the Shift-Launch tried to restore the collaboration from knowledge in the Adapt_It_WX.ini file in the …AppDataRoaming folder. But the consumer might not need collaboration restored. So now, a Yes/No message dialog will ask the consumer: “If a collaboration was set up with Paratext or Bibledit, do you want it to be restored now, if possible?”. Click the No button to have the collaboration turned off.
Bug fixes in 6.8.zero launch 1 July 2016
- Left and proper double angle quotation marks at the moment are routinely added to the source and goal punctuation character units, if not already current.
- The straight single quote, ‘ is now handled as a punctuation character by default. Earlier, it defaulted to being a word-building character.
- USFM fastened area marker ( ~ ) is dealt with higher. It still is a hard and fast area, however when occurring between a phrase and punctuation it’s stripped off and restored later like punctuation characters, and it now routinely seems as an entry within the punctuation character set in Preferences – which allows it to be stripped off and restored to the difference as one would anticipate. When occurring between words, it isn’t stripped off, but behaves as expected in maintaining the phrases collectively.
- If the anchor for a free translation was on a placeholder, and Export Free Translation was chosen, the free translation at that placeholder was misplaced from the export. It’s now included, alongside with any markers which happen there.
- When collaborating with Paratext, if the supply text in Paratext had an finish marker, akin to x*, left in the text at a location where the matching previous x marker and the cross reference info had been manually removed, then it brought on a serious drawback in the switch of adaptation text to Paratext at File > Save. All goal
text content material following the rogue x* marker wouldn’t get transferred – even if the consumer had adapted properly past that point. Code has now been added to skip such rogue markers, and the knowledge transfer now doesn’t get truncated. (Nevertheless, it’s all the time sensible to verify the supply text for markup errors earlier than establishing a collaboration with Paratext or Bibledit.)
- The function launched in 6.8.0 the place sure word-final or phrase-final punctuation characters might routinely set off auto-capitalizing the subsequent phrase (or phrase), did not work when the supply text was a language with no case distinction. Now it works appropriately in 6.8.1.
Windows and Macintosh version 6.8.1 downloads are available at:
Linux version 6.8.1 Debian packages can be found in i386 and amd64 architectures for Ubuntu Precise, Trusty, Vivid, Wily, Xenial and Yakkety. There are directions on the way to configure your Linux system to realize access to the SIL repository at:
Principally you want to obtain and set up the repository’s public key on your machine, and then arrange your Software Sources with one of the following settings relying on your Linux distribution:
deb http://packages.sil.org/ubuntu exact essential or
deb http://packages.sil.org/ubuntu trusty foremost or
deb http://packages.sil.org/ubuntu vivid primary or
deb http://packages.sil.org/ubuntu wily principal or
deb http://packages.sil.org/ubuntu xenial foremost or
deb http://packages.sil.org/ubuntu yakkety fundamental
Notice: The Ubuntu Vivid, Wily, and Yakkety distributions only have brief term help from Canonical. The Exact, Trusty and Xenial distributions are long term service (LTS) distributions which Canonical will help with bug and safety fixes for 5 years from their preliminary release.
Essential Notice: Installing version 6.8.1 will routinely exchange any beforehand put in Adapt It WX (Unicode) model from 4.0.0 by means of 6.8.zero (however present venture knowledge isn’t touched when putting in updates).
Adapt It WX is the open supply, cross-platform version of Adapt It that is based mostly on the wxWidgets framework (hence the WX in the identify).
Please direct bug reviews or suggestions on the brand new model to the Adapt It workforce. On the Adapt It Help menu you’ll be able to easily send a Drawback Report or a Feedback Report immediately from inside Adapt It (over a safe connection) – see the Help menu. For those who can’t use the Assist menu’s e mail reporting features, you possibly can send a Drawback Report or Suggestions Report to the Adapt It workforce utilizing the next e mail tackle:
Alternately, you possibly can ship an e-mail to one or more of the next staff members by way of their particular person e-mail addresses:
Invoice Martin – [email protected]
Bruce Waters – [email protected]
Erik Brommers – [email protected]
Graeme Costin – [email protected] (give attention to MacOSX)
Kevin Bradford – [email protected]
Michael Hore – [email protected]
Bob Buss – [email protected] (give attention to HTML Help system)
Jonathan Marsden – [email protected]