FieldWorks 8.1.0

Version Date: Aug. 21, 2014

This release has been superseded by a subsequent release.

This version is largely intended to fix some specific bugs that were reported in the previous stable release (FW 8.0.10). However, it also includes some internal changes that lay the groundwork for further integration between FLEx and ParaTExt. Because of the internal changes, we have bumped the minor version number (from 8.0.x to 8.1.x).

The primary new features are:

  • The “Find” function now searches in Definition and Reversal (when the user has chosen an Analysis language for the search), and those columns show in the dialog box. The Allomorph field has been hidden but is still searched and still available to be shown.
  • On importing SFM, blank \ps fields are no longer treated as if they are not there. – This prevents the sense they are in from inheriting the Part of Speech from the sense above it.
  • The Reversals field has been moved up just below the Gloss field. – This is to make it easier to track which “translation equivalents” are in each field and to ensure consistency between them when it is desired.

Bugs fixed and Improvements since 8.0.10

  • Change unspecified nasal from N to superscript n in section B. of conceptual intro.
  • Allow sorting in the Choose Natural Class dialog when choosing natural classes in environments. LT-13362
  • Choosers for Phonemes now sort the phonemes. LT-13381
  • Handle irregularly inflected variants correctly in the XAmple parser. LT-15455
  • Correct yellow screen crash when parsing all words in a text in the HermitCrab parser. LT-15438
  • Fix crash breaking into morphemes in Try-a-Word. LT-15033
  • Prevent sound and picture files from being duplicated during LIFT export. LT-15467
  • Correct erroneous support email address.
  • Fix LIFT S/R duplicating fields in examples. LT-15512
  • Fix a bug in the Change Spelling command related to tokenization issues. LT-15240
  • Fix crash when importing ParaTExt project with verse range. TE-9564
  • Fix blank reversals multiplying on import of LIFT file. LT-15516
  • Fix LIFT S/R duplicating fields in examples. LT-15512
  • Move the Reversals field just below the Gloss field in the Lexicon view. LT-15549
  • Handle enchant migration on second restore. LT-15518
  • Fix crash that can happen with a corrupt Keyman installation. LT-15533
  • Stop writing <missing font> notation to LDML files. LT-15064
  • Correct duplicated <missing font> notation in default font. LT-9684
  • Update SIL Logo. LT-15571
  • Fix a crash that occurs when a user deletes an Analysis writing system that is also a Vernacular writing system. LT-15185
  • Change behavior on an import failure after S/R Lexicon to prevent data loss. LT-15558
  • Fix some awkward scenarios in FLEx Installation on Linux. FWNX-1417
  • Fix crash if in-use Natural Class is deleted. LT-15050
  • Don’t treat blank \ps markers as missing when importing SFM files. LT-10739
  • Include Definition and Reversal in the Find Entry dialog. LT-4272
  • Process LIFT custom field data when merging examples. LT-15577
  • Add pronunciation writing systems to vernacular list on LIFT import. LT-15000
  • Stop blank reversals from multiplying during a LIFT import. LT-15516
  • Don’t crash when user attempts circular reference. LT-14613
  • Handle the sorting and filtering of subentries by type. LT-15574
  • Allow changing default project location in Linux. FWNX-1418
  • Fix crash while creating new project if select a new language as vernacular writing system. LT-15624
  • Prevent Duplicate LexRefType on S/R LIFT. LT-15619
  • Uppercase word should now match lowercase Wordform. LT-15241
  • Don’t allow deleting natural classes that are in use. LT-15050
  • Fix the padding in the “Show Dictionary Entry” box accessed from ParaTExt. LT-15557
  • “Unable to restore” warning box no longer appears if restoring with “Customized spelling dictionary files” selected. LT-15620
  • Re-enable Perl and Python converters in Bulk Process (not working since FW 7.2.7). LT-15663

  • You can collaborate on the entire project (advised) or just on the lexicon (LIFT – for use with other programs).
  • The Send/Receive Lexicon option is designed for collaborating with team members who use WeSay. Using the Send/Receive Lexicon option for sharing lexical data between FLEx users when there are no WeSay users in the team is not recommended. FLEx users should use Send/Receive Project to share the full data set, rather than using the more limited Send/Receive Lexicon, which is limited to what is covered by the LIFT format.
  • You can use both kinds of Send/Receive if you are working in a team which uses both FLEx and WeSay. In this situation, it is recommended to have only one FLEx member use Send/Receive Lexicon, and then use the Send/Receive Project to share that data with the other FLEx team members.
  • You can collaborate using a USB flash drive, an Internet server or Chorus Hub (a special network folder.)
    • Before using Send/Receive Internet using the default server, you need to go to and create a user account. For each project you want to Send/Receive, you also need to contact so they can create an online repository for you. They need the name and ISO code of the language plus whether you will be using the option Send/Receive Project (FLEx only) or Lexicon (for use with other programs).
    • When using Send/Receive Internet for the first time, you need to click the Settings button before you can use it, in order to enter the details of the remote server and the project’s repository id, etc.
    • To use Chorus Hub for local area network, one computer on your network needs to start the Chorus Hub program. Instructions are on the Settings dialog on the Chorus Hub tab.
  • Concept: all start from one copyof the project. Someone sends it. Others receive it. All can then send/receive.
    1. Someone sends it

      The person who already has the project – the master everyone is going to start working with – uses Send/Receive > Send this Project (or Lexicon) for the first time. This will create the special collaboration “repository” on the destination they choose (USB, Internet, Chorus Hub.)

      • What if there were multiple copies of the project already? Can we merge them? No, not automatically. You need to do any importing or exporting you need to do to come up with a master project which is the best version of the project. Delete the now outdated copies of the FieldWorks project from other computers.
    2. Others receive it
      • The person who doesn’t yet have the (master) project uses Get Project from a Colleague on the Welcome dialog or Send/Receive > Get Project from Colleague. This is a one-off step!
      • If you want to join a Lexicon (LIFT) repository from a project you already have in FLEx, use Send/Receive > Get Lexicon and Merge with this Project. This is a one-off step!
    3. Everyone uses send/receive to collaborate

      Once the project has been sent, and each collaborator received it the first time, all collaborators can continue to work together and share data using Send/Receive > Project, or Lexicon. The settings are saved and do not need to be re-entered. There is a toolbar button which will open the Send/Receive dialog to the last type of Send/Receive you did (project or lexicon).

  • The Messages (a.k.a. Conflict Report) will be displayed after Send/Receive if there are new messages to review. You can also open it at any time with Send/Receive > View Project Messages, or View Lexicon Messages, as appropriate.
    • Many merge-related messages are hard to understand. This is probably going to be an ongoing area of improvement, depending on feedback – how problematic the messages are in practice.
    • Send/Receive does a really good job of automatically merging data when users have changed different parts of the project. When two people have edited the same or very closely related data in the same sync cycle, send/receive keeps the data entered by the current user. A conflict message is generated and includes information of the other user’s change for comparison. If you prefer the other user’s change, you will need to copy and paste the data manually into the appropriate place in FLEx; there is not yet a tool to select one change over another and have the FLEx project automatically updated.
      • If one user adds word glosses to a text at the same time as another user adds word categories to it, this will not be merged conveniently because in the FLEx database these separate pieces of data are both part of a word’s analysis.
      • If one user modifies an entry, sense, etc. at the same time as another user deletes that same item, send/receive will keep the modification rather than the deletion.
    • If a team needs to use the global change tools in FLEx, such as Bulk Edit, merge conflicts will be reduced if the team first does a series of Send/Receives to get all sync’ed to the same state. Then one user can do the global changes, and the team then re-syncs to get those changes and continue on with their tasks.

If you have used older-style sharing over a local area network (projects have the extension fwdb), you need to turn off that way of sharing (revert to fwdata format) in order to try Send/Receive for collaborating. You can do this in File > Project Management > Project Locations and Sharing. Uncheck the box labelled “Share projects stored on this computer.”

If you want to track our progress on these and other issues, follow one of the links below and sign up for an account on our JIRA system.

  • It is strongly not recommended to restore over (replacing) an existing project with which you are collaborating using send/receive. The subsequent send/receive would send a huge number of changes to all the other team members, effectively restoring the old version of the project on every team member’s computer.
  • You cannot have non-ASCII characters in the FLEx project name to use Send/Receive.
  • The menu item “Copy (Ctrl+C)” isn’t working on the “Conflict Detail” dialog box. LT-14327
  • The Text Chart is changed incorrectly (words are moved to emptied cells) after another user deletes some charted words from the text. LT-14317
  • If both users edit the same phonemes, or add inflection features to the same lexical entry, the results may need subsequent editing. E.g. A phoneme may have incompatible phonological features and an entry may have incompatible inflection features.
  • If you add a question or add a message to a merger conflict/notification, it is not possible to edit or delete those comments subsequently. LT-14076
  • Using any Send/Receive commands in quick succession usually causes a message to pop up which claims that FLExBridge is already running. If it is not (e.g. you closed the Messages window then need to reopen them) wait for 5 seconds and try again.
  • Linked media files over 1MB in size are not being transferred. No movie files of any size are being transferred. If a user subsequently removes the link to the file due to the current restrictions, the warning messages continue to be displayed at each send/receive operation if the file is still in the project folder.
  • When both users change the properties of the same style, the resulting merge conflict message does not state the conflicting style settings.
Send/Receive Lexicon (LIFT) with e.g. WeSay
  • Send/Receive Lexicon should not be used to pass data between two or more FLEx users. You should use Send/Receive Project.
  • Send/Receive Lexicon depends on the LIFT standard. Some FLEx data is not handled well yet by this collaboration method. E.g. Which entries belong in which inflection template slots and some other morphological grammar facts stored on a lexical entry. Components of a complex form. Custom lexical relations.
  • If you created a custom field in WeSay and used a previous version of LIFTBridge with FLEx (e.g. in 2012), FLEx will crash when you try to open the project. Please contact us for help. LT-13850
Other Issues
  • In Dictionary Configuration, the check box under sense that says “display each sense in its own paragraph” is not working properly. This will be addressed in a development effort to redo Dictionary Configuration.
  • The Sena 3 (sample project) link doesn’t work on the new Welcome dialog box the first time the dialog opens. Workaround: Use Open and then select Sena 3. LT-14324
  • Semantic Domain’s Suggest feature is too prolific when there is more than one word in the Gloss field. LT-14243
  • Interlinear SFM import fails with Unicode to Unicode converter. LT-13741
  • Right-click menu is inappropriate for Status and Confidence fields. LT-14195
  • Unicode Character Editor fails to process code points out of plane 0. LT-14263
  • Type-ahead doesn’t work on custom fields referring to custom lists. LT-13248
  • To use Phonology Assistant with this version of FieldWorks, you need to upgrade Phonology Assistant to version 3.4.6 or later.
  • To use FLExTools with this version of FieldWorks, you will need to upgrade to version 1.1.4.

For Windows

A Full package contains .NET 4.0 and Windows Installer 3.1; a Minimal package does not.

Users will probably need to use a Full package if this is the first installation of FieldWorks, or an upgrade from version 7.2.7 or earlier. (This does not apply to Windows® 8.)

The SE packages only contain Language Explorer (FLEx); BTE packages also contain Translation Editor.

8.1.0 SE Full (164 MB)

8.1.0 SE Minimal (113 MB)

8.1.0 BTE Full (185 MB)

8.1.0 BTE Minimal (134 MB)

No patch is available for this version.

  1. Download one of the Full or Minimal installation packages above.
  2. Double-click the exe file you downloaded. After it extracts files, the first installation screen appears.
  3. Follow the on-screen instructions. Make sure you allow the SIL Software installer to install FLExBridge and any other required third party software it says is required.
  4. If you have used FieldWorks 6.0.6 or earlier on this computer before, you may see two further steps:
    1. Select which if any projects you wish to migrate from FieldWorks 6.0.6 or earlier format.
    2. Choose whether to uninstall the last version of FieldWorks or its desktop shortcuts. Help.

For more information on upgrading to FieldWorks 7 or 8 from an older version (6 or earlier), see here.

Please check the Known Issues section above.

Note: The movies have not yet been updated since FieldWorks 6.

Sample projects are no longer being included in the download packages. You can download them here:

  • Sena 2 – 14 MB (Lexicon and Texts for training)
  • Sena 3 – 15 MB (Lexicon and Texts data)
  • Lela-Teli 2 – 2 MB (Data Notebook for training)
  • Lela-Teli 3 – 2 MB (Data Notebook data)
  • Click one of the sample projects, such as “Sena 3″. Download and save this file to your computer. If you find that your browser (e.g., I.E.) has renamed the files to .zip, you will need to rename them first to .fwbackup in order for the FieldWorks restore function to work.
  • Launch FieldWorks Flex.
  • Open the Restore a Project dialog by doing one of the following:
    1. If the welcoming Language Explorer dialog appears, click “Restore a project from a backup file”.
    2. Or if the main FieldWorks Language Explorer window appears, choose File > Project Management > Restore a Project.
  • On the Restore a Project dialog, click “Another location” and click Browse.
  • Navigate to the downloaded sample project file (which may be in your Downloads directory by default), click the file, and click Open.
  • Click OK.

Here is the MD5 hash of each of the download packages, should you wish to use this to verify the download completed successfully.

Package MD5 hash
FW810_SE_A 131FD91C8E1364C2D68AED69BB7A6DF8
FW810_SE_B ED455718B27225827AAFDF8905536A6F
FW810_BTE_A 4E89DAC42D41338251F690FB28647EC9
FW810_BTE_B 313AE43BF4B883189B6F29109AE90F97

Recommended System Configuration
  • Operating system: Microsoft Windows® 7 with Service Pack 1
  • Computer and processor: Computer with Intel Core® (or equivalent) processor running at 2.2 gigahertz (GHz) or higher
  • Memory: 2 gigabytes (GB) of RAM or more.

Note: The more RAM and the faster the CPU, the better FieldWorks will perform, especially with larger projects.

Minimum System Requirements
  • Operating system: Microsoft Windows® XP Professional with Service Pack 3 or later, Windows Vista® with Service Pack 2 or later, Windows® 7 with Service Pack 1, Windows® 8.
  • Computer and processor: Computer with Intel Pentium® (or equivalent) processor running at 1.5 gigahertz (GHz).
  • Memory: 500 megabytes (MB) of RAM.
  • Hard disk: Hard disk space requirements will vary depending on existing machine configuration and custom installation choices. As a guideline figure, you should have at least 1.5 gigabytes free prior to installation. In any case, you are recommended to have at least 10% of your hard drive free in order to allow Windows to run properly.
  • Display: 1024 by 768 pixels screen resolution or greater (for laptops, use native display resolution).
  • Offline storage: An external USB drive, network drive, or writeable CD-ROM to allow offline data backups.
  • Peripherals: Mouse or compatible pointing device.

For SE For BTE

For Linux

This version of FieldWorks is available on both Windows and Linux. Send/Receive became available for Linux starting with 8.0.5. Data created in one can be opened (or restored) in the other, and vice versa. (Note that data created in any version cannot be opened by any older version on either platform.)
Instructions for installing the Linux version are available on the LSDev Linux wiki.

Leave a Reply