06/10/2017 - 4:30pm

Version 3.1.1 / 2.31.1 Released

A new version of XLingPaper is now available. This minor update has several fixes and some enhancements:

  • Improve Linux installers
  • Add ability to have contents in the back matter instead of in the front matter. This is controlled by a publisher style sheet.
  • Allow the presence of a contentsLayout element in a style sheet to be controlled by content control. This helps to let one have a single document where the content is in different languages and one can control whether the table of contents appears in the front matter (e.g., English) or in the back matter (e.g., French) via the content control for that language.
  • Fix Bug: Too much info showing up for Parts in FO/Word/OpenOffice table of contents.
  • Re-add Quick Reference Guide PDF that was inadvertently deleted.
  • Fix XLingPap.dtd location in SILInternationalPaperStylesheet.xml.
  • Fix bug which kept Calibre from running on Mac OS X; the result was that an EBook could not be produced.
  • For the default way of producing PDF (via XeLaTeX):
    • Fix bug: when using an index, sometimes the page numbers would always be ‘??’.
    • Fix bug: in a style sheet, when a section layout had useperiodafternumber=’yes’ and also beginsparagraph=’yes’, the section number did not have a final period.
    • Fix bug: when a td or th cell had a width attribute set, any align attribute was ignored.
06/08/2017 - 11:26am

Windows 10 Creators Update Warning

The latest major Microsoft update for Windows 10, the Windows 10 Creators Update or the 1703 update will cause the FieldWorks program to crash and reduce the performance of the Paratext program (both versions 7 and 8), especially on slower computers. If you are using any of these programs, it is therefore best to avoid this update for the time being. This is a Microsoft bug and we have talked to them about the problem. There has been a lot of discussion about this in the FLEx list Google group. If you are not a member already, you may be interested in joining. You can join by going to

Even if you are not running Windows 10, you may be vulnerable to the reduced performance of Paratext if you install any application that includes .NET Framework 4.7. If you have .NET Framework 4.7 installed, you can uninstall it by going to Start > Settings > Update & security > Update history > Uninstall updates. Then go to the Microsoft Windows section, right-click on Update for Microsoft Windows (KB3186568), and then click Uninstall.

To check the version of Windows 10 that is running, click the Start button, type About your PC, then press the Enter key. Check the information on the Edition and Version lines. If the Version line says 1703, the Windows 10 Creators Update is already installed. If that is the case, your best option is to revert to the previous Windows version, version 1607. To do that, go to Start > Settings > Update & security > Recovery. If the Creators Update was installed less than 10 days ago, you will then see an item named Go back to the previous version of Windows 10 in the right pane. Click on the Get started button under that heading to start the roll-back process. If you do not see that option, there is not much you can do other than reinstalling Windows 10.

If you are currently running Windows 10 Pro or Enterprise, version 1607, you should delay the automatic download and installation of the Creators Update. To do so, go to Start > Settings > Update & security > Advanced options (under Update settings) and check the Defer Feature Updates option. That will delay the installation of the Creators Update for several months, while you will still be getting other Microsoft updates. Hopefully the problems with the Creators Update will have been fixed before it is offered to you again.

If you are running Windows 10 Home, version 1607, the best option for getting a similar delay with the installation of the Creators Update, is to actually let Windows download and install the update first and then use the method described above to revert to the 1607 version. But remember that the roll-back must be done within 10 days of the installation. This method will also enable you to get other Windows updates while the Creators Update is put on hold for several months.

The last I heard (June 15), Microsoft has a fix for the bug and will be sending out a test version in about a month. I’m not sure of the availability of that fix, but will try to keep you informed.

05/15/2017 - 9:24pm

Adapt It version 6.8.3 now available

Adapt It version 6.8.3 release 11 May 2017

Feature changes and new features in 6.8.3

This release adds a new feature to Adapt It that will be of interest to those who are working in collaboration with Paratext or Bibledit. We call the new feature in this release “Data transfer protection for Paratext or Bibledit.”

After drafting texts in collaboration with Paratext or Bibledit, there comes a time when those texts are revised and polished within Paratext/Bibledit, and further changes from Adapt It should no longer be transferred to those texts in Paratext/Bibledit. The new feature allows the administrator to designate which books and chapters should be ‘protected’ from getting any further changes made in Adapt It. With this feature the team can bring the advanced/polished revisions from the advanced drafts back into the old Adapt It texts, in order to bring Adapt It’s knowledge base up to date, without worrying about Adapt It overwriting changes to the revised/polished drafts residing in Paratext or Bibledit. Bringing Adapt It’s knowledge base up to date makes adapting/drafting of future collaboration documents in the project much more accurate and proceed faster. And, during the updating process, the advanced drafts in Paratext/Bibledit are “protected” from getting spurious changes when the texts are saved within Adapt It’s local texts and its knowledge base.

There is now a menu item on the Administrator menu called, “Manage Data Transfer Protections to Paratext or Bibledit…”. This menu item presents the following dialog:

The dialog allows an administrator to select an Adapt It collaboration project and designate which books and chapters should no longer transfer changes made from within Adapt It to the Paratext or Bibledit version of those books/chapters. The appearance and functionality of the dialog depends on whether a collaboration project was set up to collaborate using “Chapter Only Documents” mode or “Whole Book Documents” mode. The above image shows an example of the default “Chapter Only Documents” mode.

In the dialog the administrator follows the 3 numbered steps:

  1. Selects an AI collaboration project from the drop-down list – in our example case we selected the ‘Language S to Language T adaptations’ project. The possible books appear in the ‘Books’ List.
  2. The administrator (in the above example) selects the book of Mark from the ‘Books List’ – and the dialog displays the 16 chapters of Mark in the ‘Chapters List’ with empty check boxes next to each chapter.
  3. The administrator then clicks on the “All Chapters of Book” button to put ticks in the check boxes of all 16 chapters.

As many books/chapters as desired can be designated as ‘protected’. Finally the administrator clicks on OK to save the ‘protection’ settings for all chapters of the book of Mark. The draft that exists in Paratext for that book is now ‘protected’ in the sense that any changes that get made back in the chapter documents of Mark within Adapt It will no longer be transferred to Paratext.

Some teams set up a collaboration project in Adapt It to collaborate with Paratext using ‘Whole Book Documents’ mode rather than using the default ‘Chapter Only Documents’ mode. In such cases the “Manage Data Transfer Protections to Paratext or Bibledit” dialog appears like this:

In this version of the dialog the administrator again follows the 3 numbered steps:

  1. Selects an AI collaboration project from the drop-down list – in our example case we selected the ‘Language S to Language T adaptations’ project. The possible books appear in the ‘Books’ List.
  2. The administrator (in the above example) selects the book of Mark from the ‘Books List’. The ‘Chapters List’ is disabled since in ‘Whole Book Documents’ mode, collaboration only gets whole books from Paratext, and the Adapt It documents are kept in whole books rather than individual chapters.
  3. The administrator then clicks on the check box for the book he wants to “protect” in Paratext, or alternatively selects one of the range buttons below the ‘Books List’ to select a range of books.

Finally the administrator clicks on OK to save the ‘protection’ settings for the whole book(s) selected. The draft that exists in Paratext is now ‘protected’ in the sense that any changes that get made back in the ‘protected’ book of Mark within Adapt It will no longer be transferred to Paratext, but will be saved locally in the project folder of Adapt It’s Adapt It Unicode Work’s folder.

What advantage is there to “protecting” documents from data transfers? With all the chapters of Mark ‘protected’, and after the book of Mark has been revised to an advanced state in Paratext, the team can then bring the ‘final’ revisions back into the Adapt It documents and thereby greatly improve Adapt It’s knowledge base for the project. The expanding and improving of the knowledge base makes adapting/drafting of future collaboration documents in the project much more accurate and faster. And, during the updating process, the advanced drafts in Paratext/Bibledit are “protected” from getting spurious changes when the texts are saved within Adapt It and its knowledge base.

How should the knowledge base updating take place? One way is as follows: Once the book/chapter protections are done, the administrator asks the translator to open the old Adapt It ‘Language S to Language T adaptations’ project in one desktop window, and Paratext in another window with the Language T Paratext project displaying within Paratext, so that the translator can compare the polished version in Paratext’s Language T project with the ‘target’ Language T in the old drafts in the Adapt It project. Alternatively, the administrator could print out the advanced draft and have the translator compare the printout with the old draft within Adapt It. In either case the administrator asks the translator to open each chapter (or book for whole book mode) of Mark in Adapt It and compare the old drafts with the more polished version in Paratext – and make changes in the Adapt It target language drafts to make them read as much the same as possible as the polished version.

A translation team might follow this process for each book translated, so that each collaboration book in turn can be drafted in Adapt It, the polishing work done exclusively in Paratext or Bibledit – the administrator having used this new feature to “protect” Paratext/Bibledit from any old drafts being transferred or overwriting the advanced drafts.

As described above the new feature is available to administrators for ‘bulk’ setting of books/chapters through the “Manage Data Transfer Protections for Collaboration Editor” dialog (from the Administrator menu). This protection feature is also available in a more restricted form to non-administrator users via two new menu items in Adapt It’ Advanced menu:

     Prevent Paratext/Bibledit from getting changes to this document
     Allow Paratext/Bibledit to get changes to this document

The above two menu items are enabled in the Advanced menu only when a collaboration project document is opened within Adapt It. With these menu items a user can tell Adapt It to “Prevent…” or “Allow….” changes made in the document transferring from/to Paratext/Bibledit when Adapt It saves the document. As with the bulk dialog (available from the Administrator menu), the protection status for the document is saved and remains in that protected state unless it is explicitly changed – either by using one of the two Advanced menu items or by the administrator in the bulk change dialog from the Administrator menu. The two new Advanced menu items are limited, because the user can only change the protection status of the open collaboration document, and cannot change the protection status for all chapters of a book (or whole book) without opening each chapter (or book) and invoking one of the above Advanced menu choices on the open document.

See the “Help_for_Administrators.htm” document for more details and how a collaboration scenario might play out, using this data transfer protections feature.

Windows and Macintosh version 6.8.2 downloads are available at:

Linux version 6.8.3 Debian packages are available in i386 and amd64 architectures for Ubuntu Trusty, Vivid, Wily, Xenial and Yakkety. There are instructions on how to configure your Linux system to gain access to the SIL repository at:

Basically you need to download and install the repository’s public key on your machine, and then set up your Software Sources with one of the following settings depending on your Linux distribution:

deb trusty main     or
deb vivid main     or
deb wily main     or
deb xenial main    or
deb yakkety main

The Ubuntu Vivid, Wily, and Yakkety distributions only have short term support from Canonical. The Trusty and Xenial distributions are long term service (LTS) distributions which Canonical will support with bug and security fixes for 5 years from their initial release.

If you are using Wasta Linux the software sources for installing and updating Linux software from the repository are already configured.

Important Note: Installing version 6.8.3 will automatically replace any previously installed Adapt It WX (Unicode) version from 4.0.0 through 6.8.2 (but existing project data is never touched when installing updates).

Adapt It WX is the open source, cross-platform version of Adapt It that is based on the wxWidgets framework (hence the WX in the name).

Please direct bug reports or feedback on the new version to the Adapt It team. On the Adapt It Help menu you can easily send a Problem Report or a Feedback Report directly from within Adapt It (over a secure connection) – see the Help menu. If you cannot use the Help menu’s email reporting functions, you can send a Problem Report or Feedback Report to the Adapt It team using the following email address:

Alternately, you can send an email to one or more of the following team members via their individual email addresses:

Bill Martin      –
Bruce Waters     –
Erik Brommers    –
Graeme Costin    – (focus on MacOSX)
Kevin Bradford   –
Michael Hore     –
Bob Buss         – (focus on HTML Help system)
Jonathan Marsden –
03/14/2017 - 10:31am

Dictionary-making workshop for the Gusilay in Senegal

(March 2017) In the town of Thionck-Essyl in the south of Senegal, speakers of the *Gusilay language are celebrating the success of the recent Rapid Word Collection (RWC) workshop, an updated approach to jump-starting the making of a dictionary. The workshop was publicized on the local radio station, including interviews of participants who voiced the importance of their collective work. The broadcast resulted in a room full of Gusilay speakers at the closing ceremony, ready to join the celebration.


Read the full article at

07/26/2016 - 7:59pm

Keyman @keyman

@RH_IQ_Keyboard no, Keyman is not designed to use an alternate dll. Even Keyman's European layout support would not do what you are asking.
04/22/2016 - 5:44pm

Release Pathway 1.14.2 Hotfix

Pathway 1.14.2 is a hotfix to Pathway 1.14.1. It includes some additional files necessary to build Sword modules that were inadvertently left out of the 1.14.1 stable release.

04/18/2016 - 4:56pm

Spelling Restrictions Removed in Version 2.1

In response to User feedback, nearly all restrictions have been removed from the characters allowed in kin terms and in names. All characters in all UTF character sets are now legal, including hyphens, embedded blanks, numbers, and special characters.

Only double-quotes and commas are prohibited in the body of a kin term; numbers and asterisks may not be the first character of a kin term.

02/02/2015 - 5:52pm

WeSay 1.5 release version

WeSay 1.5 is now considered the official “release version”. The Windows version can be downloaded here:

and there are installation instructions for Linux on the downloads page.

Most of the known bugs have been fixed. However, do check out our “Known Issues” below.

New since the Release Candidate version

  • Fixed a minor display problem for task tabs in localized versions.

Known Issues in WeSay 1.5

  • When doing Send/Receive, sometimes it times out after 900 seconds (15 minutes).
  • In order to display most non-roman scripts on Linux, you will need to turn on GeckoFX. (On Windows, GeckoFX is only needed for Graphite fonts.) However, there are a number of issues with Gecko on Precise. If you need non-roman support, at this point we recommend using Trusty with Gecko turned on. However, there still may be some issues with automatic keyboard switching and tabbing between fields (need to tab twice).
  • Not all controls have been converted to use Gecko, so on Linux some will still display boxes for certain non-roman scripts. Some examples include: the History report for Send/Receive and the keyboard test area in the WeSay Configuration Tool.


03/14/2013 - 5:35pm

SayMore at the ICLDC 2013

I recently had a stimulating time at the 3rd International Conference on Language Documentation and Conservation at the University of Hawaii. There are so many warm, friendly, and energetic people working in this space.

Here’s the presentation I gave:

06/24/2009 - 4:58pm


Paratext 8 Released

Visit the Paratext 8 website to find out how to register for and download Paratext 8.0.

About Paratext Translation & Publishing Software

Paratext and related tools are a collection of software programs for Windows and Linux developed jointly by the United Bible Societies and SIL International which allow you to input, edit, check, and publish a translation of the Scriptures, based on the original texts (Greek, Hebrew), and modeled on versions in major languages.

A growing body of scripture translation text in the USFM format is the basic unit around which all of the Paratext tools, utilities, and companion programs operate.

For more information, please click on the following links.

Register for Paratext 8!

Paratext has been developed by UBS and SIL primarily for use by translation and publishing project teams. It is also available with some functionality restrictions to any person. Copyright restrictions, especially those determined by third party copyright holders, require that use and distribution of Paratext text resources be strictly limited to those engaged in the Bible translation and publishing process.

New users:  Use of Paratext 8 and associated software requires registration for Paratext 8.

Existing users:  Existing users of Paratext 7 should re-register for Paratext 8 using their Paratext 7 registration details. (For teams that are already using Paratext 7 and need to register additional users, it is still possible to register for Paratext 7.)



read more