FieldWorks 8.3.2 Beta 2
Version Date: Dec, 16 2016
The new FieldWorks website is now live. The link is now http://software.sil.org/fieldworks/. We are working on a redirection from here, but in the meantime, click on this link to go to the new site. To look at this page on the new site, click here
THIS IS A BETA RELEASE.
It contains a model change relative to FW 8.3.1.
Note: We discovered a significant problem in how FW 8.3.1 Beta 1 handles variants and complex forms. In order to fix this problem, we had to make another model change. We highly recommend that anyone using FW 8.3.1 Beta 1 upgrade to FW 8.3.2 Beta 2 as soon as possible.
Please make a backup of your project before uninstalling your current version of FieldWorks and store it in such a way that you know what version of FieldWorks made the backup.
Because this version of FieldWorks contains a model change, any projects opened in it will no longer work with previous versions (including FW 8.3.1 Beta 1 and FW 8.3.0 Alpha). If you use Send/Receive, all collaborators must upgrade if any of them do.
When you make backups, we recommend that you store them in such a way that you can tell what version of FieldWorks made the backup. For instance, you may choose to have subfolders within your Backups folder, one for each version of FieldWorks, such as FW 8.2, FW 8.3.0 Alpha 3, FW 8.3.1.)
Note that FW 8.3.0 Alpha 3 did not include a model change relative to FW 8.2.8, and there had not been one since FW 8.0.4. Thus, projects created in any version between 8.0.4 and 8.3.0 Alpha 3 could all be opened by any of those versions. However, projects opened in FW 8.3.1 Beta 1 cannot be opened by FW 8.3.0 Alpha 3 (or any earlier version), and projects made in FW 8.3.2 cannot be opened by FW 8.3.1 Beta 1 (or any earlier version)..
The primary new features in FieldWorks 8.3 are:
- One-button upload to Webonary. Once you have an account at webonary.org, it is now as easy as configuring your credentials, choosing what you want to publish, and clicking a button, to upload your data to Webonary. To upload a newer version of your data, just click that button again.
- New fields
- Enhanced Etymology cluster: is now explicit about the difference between Source Language and Bibliographic Source. Also includes enhanced comment and note fields. Languages can be expressed as list items (new list in the Lists area) or free-form.
- Dialect Labels (entry and sense): a new list field to allow you to annotate headwords and senses as to which dialect they occur in. Set up the list of dialects and their abbreviations in the Lists area.
- Extended Note: a special kind of note that allows you to include example sentences as part of the note. The whole note (including examples) can be displayed in its own paragraph.
- Publish In fields for Pictures and Pronunciation.
- Restrictions field now allows embedded writing systems.
- New version of the Configure Dictionary functionality, featuring:
- WYSIWYG dictionary previews. Now the Dictionary view is showing you (nearly) exactly what you will see on Webonary.
- A preview pane right in the Configure Dictionary dialog.
- A highlight button so you can see what content is affected by the node you are configuring.
- The ability to enter Unicode values in the Before/After boxes.
- Enhanced ability to duplicate and rename nodes.
- All-around better reliability and consistency for all configuration nodes, and a foundation that will allow the developers to add features much more easily than was possible before this version.
- Enhanced ability to manage custom configurations and link them to publications.
- Built-in shared configuration for some of the nodes.
- Separate nodes for Minor Entries that are Variants versus Complex Forms (and for Main Entries that are Complex Forms, in stem-based views). ((In the Alpha and Beta 1 versions, these need to be configured separately from each other and from the Main Entry. In the future, it will be possible to indicate whether they should share another node’s configuration or be configured separately.)
- Better connection between Reversal Indexes and Publications.
- Publication menu in Reversal Index view.
- New “unidirectional” lexical relation that allows you to display the link on only one of the linked entries.
- New “unspecified” Complex Form Type and Variant Type, to prevent confusion over items that are non-obvious complex forms.
- Stem-based view is now called Lexeme-based view.
- Abbreviation and Reverse Abbreviation have now been swapped in Variant Types list.
- When an entry has more than one item with the same complex form type, the type is only shown once, with all the forms after it.
- New configuration possibilities:
- Option for Senses to be displayed in separate paragraphs allows choice of whether the option applies to the first sense or not.
- Subsenses can be configured separately from Senses.
- More choices for Sense and Subsense numbering.
- Examples and Notes can be displayed in separate paragraphs.
- Names of nodes in Reversal configuration have been adjusted.
- New default styles available to configure the reversal index differently from the main dictionary.
- New node “Gloss or Summary Definition”, to more easily configure a reference that could point at either a Sense or an Entry.
- Pictures can now have the Headword or Gloss of their sense as the caption.
- A “References Section” that allows you to group several configuration nodes so formatting can be applied to the group as a whole.
- Improvements to the default configurations (spacing and punctuation).
- Hybrid view: A new default configuration that is a cross between root-based and stem-based views. This view is based on the work of Bartholomew & Schoenhals’ Bilingual Dictionaries for Indigenous Languages1 Some of the key features of this layout include:
- Information of greater interest to the language community comes first in the entry; information for academic linguists is last.
- Complex forms are presented as main entries (like stem-based views), but it also includes “minor subentries”, to show minimal information about the complex form right in the main entry (like root-based views). There is an emphasis on clearly delineating the different kinds of information in the entry.
1Bartholomew, Doris A. and Louise C. Schoenhals, Bilingual Dictionaries for Indigenous Languages. Instituto Lingüístico de Verano, México, D.F., 1983.
Bugs fixed since 8.3.1 Beta1
- LT-17913, LT-17775, LT-17959 Fix migration problem that put “unspec. var.” on complex forms.
- LT-17909 Shared nodes in dictionary config dialog should always be enabled.
- LT-17945, LT-18019 Add help topics for Bulk Edit for new fields.
- LT-17894 “Show Gram Info first” now behaves the same as in 8.2.8.
- Implement Bulk edit for Extended Note.
- LT-17932 Bug Fixes for Bulk Edit Publish In (Pictures, Pronunciations).
- LT-16240 Make the Archive With Ramp dialog localizable.
- LT-17970, LT-17973 Correct issues that caused some projects to not open in 8.3.1 Beta.
- LT-17934 Correct Bulk Edit Etymology problems.
- Update the Ethnologue library content.
- Make sure pejorative language names do not show up in the Writing Systems setup dialog.
- LT-18008 Correct errors when editing in FLEx associated with Paratext.
- LT-17956 Right-click Sense numbers to configure proper node.
- LT-17982 Bad etymologies in an old configs no longer cause crash.
- LT-17900 Etymology cluster is now migrating properly.
- LT-17906 Improve logic for “number even a single sense”.
- LT-17762 Sort variants alphabetically.
- LT-17980 Correct WS problem to prevent crash.
- LT-18015 Correct data corruption problem with Unidirectional Lexical Relation after moving or deleting item.
- Don’t crash inserting a sense when the entry has bad morph data.
- LT-17993 Fix Letter headers in the FW 8.3.1 exports.
- Fix alignment in interlinear export to XLingPaper.
Bugs fixed since 8.3.0 Alpha3
- LT-10904, LT-10579 Allow user to decide whether SFM import creates new entries for missing link targets.
- LT-12305 Lay out embedded bidi elements on a “per field” basis, not treating sequences as a single run.
- LT-12569 Add “Pronunciation-Media File” as a column in Browse views.
- LT-15138 Don’t create duplicate cross references on import, if source file had them on both entries.
- LT-15705 Honor name/abbreviation custom list display setting in slice.
- LT-16909 Add Media Files to Pronunciation in Reversals.
- LT-16934 Bring back the custom line break character.
- LT-17019 Fix crash in Lexicon Edit while using English (Audio).
- LT-17264 Writing System Abbreviations now obey the Writing System Abbreviation style.
- LT-17384 Reversal export now produces results in the same order when run more than once.
- LT-17441 Maintain order of subentries from SFM import.
- LT-17449 Disallow empty Complex Form Type.
- LT-17507 Fix Fontinfo overrides for all Writing Systems.
- LT-17564 Correct Bulk Editing Morph Type producing bad data.
- LT-17574 Update to GeckoFX 45 for improved bidi display.
- LT-17611 Fix suffix letter header problem in export to Pathway.
- LT-17615 Increase timeout value when uploading to Webonary.
- LT-17669 Embedded writing systems now get color from their own default style, instead of the surrounding writing systems.
- LT-17719 Allow choosing a paragraph style for Main Entry, so there can be separate styles for LTR and RTL.
- LT-17720 Make “At Least” and “Exactly” line spacing the same for now.
- LT-17785 Upload to Webonary doesn’t display the correct counts.
- LT-17801 Letter headers weren’t showing if Headword column was sorted on a specific writing system, rather than “default”.
- LT-17846 Automatically refresh previews.
- LT-17864 Reversals were showing nothing if nothing referenced the main reversal.
- LT-6248 Reversal Entries entered in Subsenses now appear in the Reversals column of Entries in Lexicon Edit or Browse.
- Added French translations of most new UI strings.
- Updated Spanish localization.
Bugs fixed since 8.2.8
- LT-13041 LT-13041 Variant Comments can now be viewed/edited in Bulk Edit.
- LT-17340 Option to attach audio files now includes .mp4.
- No longer necessary to “Insert Reversal Index”. They automatically exist for all analysis languages.
- LT-4443 Make Sense columns in Browse views show Subsenses along with Senses.
- LT-17208 Activate spell checking in Bulk Edit Reversal Entries.
- LT-15989 Don’t print letter headings when dictionary is sorted on something other than the Headword.
- LT-17385 Fix a yellow box error when parsing with the XAmple parser and showing details.
- Various other parser fixes.
- LT-14995, LT-14996 Fix spacing in semantic domain worksheets.
- LT-11388 Fix writing system problem with “Find Example Sentence” in a vernacular writing system that isn’t currently the primary one.
- Enhance the HTML export of interlinear texts.
- 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 languagedepot.org and create a user account. For each project you want to Send/Receive, you also need to contact email@example.com 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.
- 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.
- 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!
- 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).
- Someone sends it
- 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.
Known Issues with the Beta version
- Translation Editor does not start up.
- More improvements to the default configurations are still needed.
- We plan to make it possible to choose whether Main Entry (Complex Forms) shares its configuration with Main Entry or not.
- “At least” and “Exactly” settings for line spacing currently behave the same.
- There are still some Style inheritance problems.
- When using ChorusHub, it must be run on a Windows machine. Running it from a Xenial machine doesn’t work reliably.
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
A Full package contains .NET 4.0 and Windows Installer 3.1; a Minimal package does not.
Users can probably use the minimal package unless this is the first installation of FieldWorks and their operating system is older than Windows® 8.
No patch is available for this version.
- Download one of the Full or Minimal installation packages above.
- Double-click the exe file you downloaded. After it extracts files, the first installation screen appears.
- 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.
- If you have used FieldWorks 6.0.6 or earlier on this computer before, you may see two further steps:
- Select which if any projects you wish to migrate from FieldWorks 6.0.6 or earlier format.
- 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.
- 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:
- If the welcoming Language Explorer dialog appears, click “Restore a project from a backup file”.
- 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.
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, Windows® 10.
- 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.
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.