Note

Report as inappropriate Your report has been received

Shared by: HC120704015212

Tags

Stats

views:: 7
posted:: 7/3/2012
language:: Portuguese
pages:: 21

Public Domain

Document Sample

FieldWorks 6.0 ReadMe 1

FieldWorks 6.0 ReadMe
Contents
FieldWorks 6.0 ReadMe ................................................................................................................. 1
System requirements ................................................................................................................... 3
Custom keyboards ....................................................................................................................... 3
Using Spelling Dictionaries with FieldWorks .......................................................................... 10
Known issues ............................................................................................................................ 11
Potential issues .......................................................................................................................... 18
Technical support ...................................................................................................................... 21
Acknowledgements ................................................................................................................... 21

SIL FieldWorks applications
The vision of SIL FieldWorks is to provide an integrated set of software tools which support a
variety of tasks in language projects, for both cross-cultural workers and members of a language
community. The tasks range from collecting, organizing, and managing language and culture
data, to publishing a variety of works, including dictionaries, annotated texts, culture notes, and
other works. Each FieldWorks software tool uses the same underlying database to integrate
culture and linguistic tasks.
SIL FieldWorks 6.0 consists of Data Notebook 2.14, Language Explorer 3.0, Topics List
Editor 2.14, and WorldPad 2.14.
 Data Notebook provides a method to record, organize, and analyze cultural data in a way
that is useful for language study, and technical publication. It is used with Topics List
Editor, used to create and modify lists to categorize notebook entries.
 Language Explorer provides lexical and text tools. It currently provides tools to support
dictionary development, morphological analysis and parsing, interlinearization and text
charting.
 WorldPad is a simple word processor that uses the SIL-developed Graphite program to
display complex scripts. WorldPad can save a file as plain text or Extensible Markup
Language (XML).

What’s New in FieldWorks 6.0
For an in depth list of changes in each of the FieldWorks applications, please read their
respective readme documents. The locations of these documents is given below.

ReadMe files
For what’s new, known issues and late-breaking information about FieldWorks applications, see
the ReadMe files. To open the ReadMe file for a FieldWorks application, do either of the
following:

e5f46ed4-1fbd-4681-8f48-c699fea09843.rtf Edited on 7/3/2012 8:02:00 PM
FieldWorks 6.0 ReadMe 2

 On the taskbar, click Start, point to Programs or All Programs, point to FieldWorks, point
to application name, and then click View the application name ReadMe file.
 Navigate to the folder for the FieldWorks application, and then open the ReadMe file.
Application Folder ReadMe file
Data Notebook C:\Program Files\SIL\FieldWorks\Data Notebook DNReadMe.rtf
Topics List Editor
Language Explorer C:\Program Files\SIL\FieldWorks\Language FLExReadMe.rtf
Explorer
WorldPad C:\Program Files\SIL\FieldWorks\WorldPad WPReadMe.rtf

To open this ReadMe.rtf file again later: On the taskbar, click Start, point to Programs or All
Programs, point to FieldWorks, and then click View the FieldWorks ReadMe file.

FieldWorks projects
A FieldWorks project is a database that stores data and text related to a particular language and
the people that speak it. All FieldWorks applications, except WorldPad, can store information in
a project. Use only one FieldWorks project for a particular language.
Back up your FieldWorks project regularly to protect the data. We recommend that you back up
your project immediately after you create it before adding data. On the File menu, point to
Project Management, and then click Backup and Restore. If you back up projects to a local
disk, make sure to back up the FieldWorks backup folder regularly to a network drive or
removable disc drive.
Unless you are an expert database manager, do not try to move or copy the database file itself.
Instead, make backups using the Backup and Restore command in any FieldWorks program.
To move a project from one computer to another, search for Copy a FieldWorks project from
another computer in the online Help for any FieldWorks application.
Whenever you upgrade to a newer version of FieldWorks, your project is upgraded to make it
compatible with the newer version. If this process ever fails, contact flexerrors@sil.org for help.

Backup file names
Do not modify the name of a FieldWorks backup file. Each backup file has a unique name that
includes the project name and the date and time, in a specific format (e.g. Sena 3 2006-10-29
1645.zip). If you change the name of a FieldWorks backup file, FieldWorks might not recognize
the backup file or restore from it.
If someone has changed the name of a FieldWorks backup file, you can correct it by using the
format ProjectName YYYY-MM-DD TTTT.zip. Open the zip file and look at the name of the .bak
file. The ProjectName is the name of the .bak file (without the .bak extension). The date and time
digits can be any valid date.

e5f46ed4-1fbd-4681-8f48-c699fea09843.rtf Edited on 7/3/2012 8:02:00 PM
FieldWorks 6.0 ReadMe 3

System requirements
Recommended system configuration
 Operating system: Microsoft Windows® XP Professional with Service Pack 2 or later,
Windows Vista® with Service Pack 1 or later, or Windows® 7.
 Computer and processor: Computer with Intel Pentium® (or equivalent) processor running
at 2.2 gigahertz (GHz) or higher
 Memory: 2 gigabyte (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 2 or later,
Windows Vista® with Service Pack 1 or later, or Windows® 7.
 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. When none of the required software is present,
1.5 gigabytes are required for installation, with a further 300 megabytes required to run the
program once installed. This can be reduced by clearing features from the FieldWorks
installer wizard. If required supporting software is already present (for example, the
Microsoft .NET Framework 2.0 SP1), the required disk space is reduced. However, if
upgrading from an earlier version of FieldWorks, even more space could be required if you
have large amounts of data (more than a few tens of megabytes).
 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.

Custom keyboards
Windows provides many built-in keyboards for typing major languages. These can be enabled in
the Control Panel under the Regional and Language Options option.
If Windows does not provide a built-in keyboard that works for your language, then you will
need to install a custom keyboard. This allows you to type text in other languages without
changing your physical keyboard. There are two basic methods for installing custom keyboards.

e5f46ed4-1fbd-4681-8f48-c699fea09843.rtf Edited on 7/3/2012 8:02:00 PM
FieldWorks 6.0 ReadMe 4

 Keyman. If you already use Keyman 6.2, it will continue to work with FieldWorks on
Windows XP. For new Keyman users, or those who wish to upgrade, Keyman 7.1 is
available for download from http://www.tavultesoft.com/70/download.php. There are
several editions to choose from. All of them require that you purchase a license within
30 days of installation. (Note: there are no longer any free editions of Keyman.) For
more information on the Web, go to www.tavultesoft.com/keyman/editions.php.
FieldWorks provides a Keyman keyboard developed by the Non-Roman Script Initiative
(NRSI) for typing IPA characters. The file to install is c:\Program
Files\SIL\FieldWorks\Keyboards\IPA\Keyman\IPAUni11.kmp. If you need the UK version
of this keyboard, download it from http://scripts.sil.org/UniIPAKeyboard.
 Microsoft Keyboard Layout Creator (MSKLC). You can download a free version of
MSKLC from http://www.microsoft.com/globaldev/tools/msklc.mspx. MSKLC allows
you to create, modify, and install custom keyboards without any purchases. If you have
an existing MSKLC keyboard, you can install that without downloading the MSKLC
package. You only need the full package to create or modify existing keyboards.
FieldWorks provides a MSKLC keyboard developed by the NRSI for typing IPA
characters. The file to install is c:\Program
Files\SIL\FieldWorks\Keyboards\IPA\MSKLC\ipa101\setup.exe. If you need the UK
version of this keyboard, check to see whether the following Web site has it available for
download: http://scripts.sil.org/UniIPAKeyboard.
The following chart makes some comparisons between Keyman and MSKLC.
Features MSKLC Keyman

Can map a single key (with various shift states) to any single Unicode value yes yes

Can map a single key to multiple Unicode values yes yes

Any key can be designated a dead key and any single key following the dead key can be yes yes
mapped to a single Unicode code point

Can map two or more keystrokes to a single Unicode code point (without the dead key no yes
approach)

Can map keystrokes to Unicode code points above Plane 0 (the application must also be able yes yes
to handle Plane 0 and higher)

Context sensitive input no yes

Can replace previously output characters no yes

Can do reordering, for example so that a prevowel is typed before a consonant but stored no yes
after it

Can enforce normalization in keyboard no yes

Works with: SIL FieldWorks, MS Office, OpenOffice, ZEdit, Toolbox 1.5, etc. yes yes

Works with: Paratext and older Toolbox no yes

Freely downloadable yes no

Use any existing Windows system keyboard as a starting point yes no

Functions on Win9x no yes

e5f46ed4-1fbd-4681-8f48-c699fea09843.rtf Edited on 7/3/2012 8:02:00 PM
FieldWorks 6.0 ReadMe 5

Using Keyman in FieldWorks
Tavultesoft Keyman is a computer program that allows you to type text in other languages
without changing your physical keyboard.
To make FieldWorks select the correct writing system and Keyman keyboard automatically:
1. Install Tavultesoft Keyman. (download from http://www.tavultesoft.com/70/download.php)
2. Install a Keyman keyboard using the Keyman Configuration program.
3. In Microsoft Windows, add an input language (also known as an input locale).
4. In FieldWorks, select the input language and keyboard for a writing system.

Add an input language (Windows XP)
From within FieldWorks you can bypass steps 1-4a by clicking the blue Windows keyboard
settings link in the Keyboard tab of the Writing System Properties page. When enabled, you can
also right-click the language button in the system tray and choose Settings to do the same thing.
1. On the taskbar, click Start, point to Settings, and then click Control Panel.
2. Double-click Regional and Language Options.
The Regional and Language Options dialog box appears.
3. Click the Languages tab, and then click Details.
The Text Services and Input Languages dialog box appears.
4. Click the Settings tab, and then click Add.
The Add Input Language dialog box appears.
5. In the Input language list, select a language that you do not use for any other purpose (for
example, Icelandic). The input language is an arbitrary choice, but it must be unique.
Tip: Select a language name that reminds you of the keyboard. For example, Icelandic for
typing the International Phonetic Alphabet (IPA).
6. In the Keyboard layout/IME list, select the Keyman keyboard and then click OK.
A Keyman keyboard assigned in this way should also have ‘Tavultesoft Keyman’ (Keyman
6) or ‘Tavultesoft Keyman Desktop TSF Addin’ (Keyman 7) as another option in the
Keyboard section. This line enables Text Services Framework in Keyman and is required for
proper operation of some Keyman keyboards in FieldWorks. If it is not there, add it to the
Keyboard section.
 For Keyman 6, click the Keyboard label for your language, then click the Add button and
choose Tavultesoft Keyman in the Keyboard layout/IME combo.
 For Keyman 7, you need to have at least Keyman version 7.0.241.0 or higher for this to
work. After you have defined all of the input languages you need, then go to the Keyman
configuration dialog. If you are in the FieldWorks Writing System Properties dialog, you
can do this by clicking the blue Keyman Configuration link. In the Keyman
Configuration dialog, click Addins, then under kmtip click the Configure button, then

e5f46ed4-1fbd-4681-8f48-c699fea09843.rtf Edited on 7/3/2012 8:02:00 PM
FieldWorks 6.0 ReadMe 6

click OK to the dialog that adds TSF to installed languages. You’ll need to repeat this
step any time you add a new input language for Keyman use.
Exception: Keyman 7 Light and the earlier free version of Keyman 6.2 do not provide
options for selecting the Keyman keyboard or Tavultesoft Keyman in this combo. For these
keyboards, US is usually the best keyboard choice.
7. On the Text Services and Input Languages dialog box, click OK.
8. On The Regional and Language Options dialog box, click OK.

Select the input language and keyboard for a writing system (FieldWorks)
1. On the File menu, point to Project Management, and then click FieldWorks Project
Properties.
The FieldWorks Project Properties dialog box appears.
2. Click the Writing Systems tab.
3. Select the writing system to use with the Keyman keyboard, and then click Modify.
The Writing System Properties dialog box appears.
4. Click the Attributes tab.
5. In the System Language for keyboard input list, select the input language that you added
in Microsoft Windows.
6. In the Keyman keyboard list, select the keyboard you installed.
7. Click OK.
8. To select the input language and keyboard for another writing system, go to step 3.
Keyman 7 Notes
Keyman 7 has an option in the Configuration dialog that can cause the automatic writing system
selection in FieldWorks to fail. In the Options tab, in the Advanced section, there is a checkbox
for Switch Windows language when a Keyman keyboard is selected. When using
FieldWorks, if this is checked, you may find that the correct writing system is not selected when
you click in different fields. Clearing this checkbox will solve the problem as long as other
things are configured properly.
Some versions of Keyman 7 have sticking shift problems which will interfere with entering the
desired characters and may affect the ability to use certain functions in programs. This problem
has been fixed in Keyman 7.1.268. If you experience this problem, download and install the
latest version.

Examples of writing systems, input languages, and Keyman keyboards
The following example is for a language with orthographic and IPA writing systems.
FieldWorks writing system Input Language Keyman keyboard
French French (France) None

e5f46ed4-1fbd-4681-8f48-c699fea09843.rtf Edited on 7/3/2012 8:02:00 PM
FieldWorks 6.0 ReadMe 7

French (IPA) Slovenian IPA Unicode 1.1.5

The following example does not work correctly, because one input language is selected for two
writing systems that use different keyboards. For a Keyman keyboard, the input language is an
arbitrary choice, but it must be unique.
FieldWorks writing system Input Language Keyman keyboard
French French (France) None
French (IPA) French (France) IPA Unicode 1.1.5

The following example does work, because one input language is selected for two writing
systems that use the same Keyman keyboard.
FieldWorks writing system Input Language Keyman keyboard
French French (France) None
French (IPA) Slovenian IPA Unicode 1.1.5
English English (United States) None
English (IPA) Slovenian IPA Unicode 1.1.5

The following example is for multiple Keyman keyboards.
FieldWorks writing system Input Language Keyman keyboard
Northern Yi Faeroese Yi keyboard
Northern Yi (IPA) Icelandic IPA Unicode 1.1.5
Northern Yi (Pinyin) Estonian Yi Pinyin
Chinese (Pinyin) Polish Pinyin

See below for known issues involving Keyman.

e5f46ed4-1fbd-4681-8f48-c699fea09843.rtf Edited on 7/3/2012 8:02:00 PM
FieldWorks 6.0 ReadMe 8

Using MSKLC in FieldWorks
Microsoft Keyboard Layout Creator is a computer program that allows you to type text in other
languages without changing your physical keyboard.
To make FieldWorks select the correct writing system and MSKLC keyboard automatically:
1. Install a MSKLC keyboard (e.g., c:\Program
Files\SIL\FieldWorks\Keyboards\IPA\MSKLC\ipa101\setup.exe).
2. In Microsoft Windows, add an input language (also known as an input locale).
3. In FieldWorks, select the input language for a writing system.

Add an input language (Windows XP)
1. On the taskbar, click Start, point to Settings, and then click Control Panel.
2. Double-click Regional and Language Options.
The Regional and Language Options dialog box appears.
3. Click the Languages tab, and then click Details.
The Text Services and Input Languages dialog box appears.
4. Click the Settings tab, and then click Add.
The Add Input Language dialog box appears.
5. In the Input language list, select a language that you do not use for any other purpose (for
example, Icelandic). The input language is an arbitrary choice, but it must be unique.
Tip: Select a language name that reminds you of the keyboard. For example, Icelandic for
typing the International Phonetic Alphabet (IPA).
6. In the Keyboard layout/IME list, select the keyboard installed by MSKLC (e.g., IPA
Unicode 5.0c (ver 1.0) MSK), and then click OK.
7. On the Text Services and Input Languages dialog box, click OK.
8. On The Regional and Language Options dialog box, click OK.

e5f46ed4-1fbd-4681-8f48-c699fea09843.rtf Edited on 7/3/2012 8:02:00 PM
FieldWorks 6.0 ReadMe 9

6. The Keyman keyboard list should be set to None.
7. Click OK.
8. To select the input language and keyboard for another writing system, go to step 2.

e5f46ed4-1fbd-4681-8f48-c699fea09843.rtf Edited on 7/3/2012 8:02:00 PM
FieldWorks 6.0 ReadMe 10

Using Spelling Dictionaries with FieldWorks
FieldWorks Language Explorer will automatically make use of Open Office 2.X spelling
dictionaries to check the spelling if you have Open Office 2.X installed. FieldWorks is
incompatible with Open Office 3.X spelling dictionaries.
Even without Open Office 2.X installed, you can download Open Office 2.X spelling
dictionaries for use with FieldWorks. These spelling dictionaries can be obtained free from:
http://wiki.services.openoffice.org/wiki/Dictionaries.
Save the unzipped dictionary files to:
Windows XP: C:\Documents and Settings\<username>\Application Data\Enchant\MySpell
Windows Vista: C:\Users\<username>\AppData\Roaming\Enchant\MySpell

FieldWorks uses Enchant to check spelling.
More information and options for configuring Dictionaries to use with Enchant can be found
here, but is not FieldWorks-specific.

To begin using this functionality to check the spelling of vernacular texts, for which we presume
there is no commercially available spelling dictionary, click the following in Language Explorer:
Tools>Spelling>Show Vernacular Spelling Errors.
You will need to specify which words are correctly spelled, which you can do in selective bulk
operations by using Tools>Spelling>Edit Spelling Status.
Red squiggles indicate an incorrect or unknown spelling status. Blue squiggles indicate that
FieldWorks is unsure which writing system the word is in. Select the correct writing system in
the toolbar writing system chooser.

e5f46ed4-1fbd-4681-8f48-c699fea09843.rtf Edited on 7/3/2012 8:02:00 PM
FieldWorks 6.0 ReadMe 11

Known issues
Compressed directories or files
SQL Server will not work properly if any of the data directories are compressed. In particular,
Application Data\SIL\FieldWorks\Data must not be compressed. If it is, FieldWorks will be
unable to open a language project. In general, you will probably have better performance if none
of the program or data directories used by FieldWorks are compressed. FieldWorks will now
detect this directory being compressed and will attempt to uncompress it during installation.

Backup files (XML and DTD)
If you select the Include a human readable (XML) backup check box on the Backup tab of the
Backup and Restore dialog box, FieldWorks includes an XML file in the project backup file,
which is a Zip file. If you extract the XML file from the Zip file, and then open it in Internet
Explorer, the following message appears: Cannot view XML input using style sheet. Please
correct the error and then click the Refresh button, or try again later.
Solution: The XML file refers to a Document Type Definition (DTD) file that must be in the
same folder. Copy the FwDatabase.dtd file from C:\Documents and Settings\All
Users\Application Data\SIL\FieldWorks\Data, and then paste it into the folder containing the
extracted XML file. Alternatively, open the XML file in ZEdit.exe, installed in your c:\Program
Files\SIL\FieldWorks directory.

Backup – scheduling on Windows Vista, or on XP as a non-administrator
If you attempt to schedule a backup, and you are running FieldWorks without administrative
privileges, you will get an error message saying the Task Scheduler cannot be configured. This is
because configuring Task Scheduler is an administrative task. The following work-arounds are
suggested:
 On Windows XP: log off, and log on as an administrator. Then launch FieldWorks and
configure the backup schedule. Afterwards, you can log back on as the original user.
 On Windows Vista, launch FieldWorks by right-clicking on the application shortcut, and
selecting “run as administrator” from the pop-up menu. After you have configured the
backup schedule, you can quit the application, and start it again in the normal way.

Backup – scheduling without a password
If you attempt to schedule a backup, and your user account does not need a password to log on to
Windows, the Backup Schedule Password dialog box will not allow you to use the blank
password. You will not be able to schedule a backup.

Colors
Some combinations of Windows system colors might appear strange in FieldWorks.

e5f46ed4-1fbd-4681-8f48-c699fea09843.rtf Edited on 7/3/2012 8:02:00 PM
FieldWorks 6.0 ReadMe 12

Editing a project on network computers
When two or more users open the same FieldWorks project on network computers, we
recommend that you avoid simultaneous editing of one entry. Edits on one computer might not
appear on the other computers. The other computers might stop responding.
 To release the other computers from the locked state, do one of the following on the
computer where the edits occurred:
 Navigate to another entry.
 On the File menu, click Save.
 To maintain synchronization, press F5 (refresh) frequently.
 If a Data Notebook user on one network computer adds a view to a project, the view will not
be available on other network computers, unless users exit, and then open the project again.
When you open a project on a server computer from a client computer, the following error
message might appear: pc_name\SILFW does not have any data. This is probably related to
firewall protection. See the firewall section below for solutions to this.
When you navigate to a FieldWorks project on a network computer in the Open dialog box,
select it, and then click Open, the project might not open. This may be due to the host computer
having SQL Server 2005 installed in addition to the version of SQL Server (MSDE) that
FieldWorks used to use. Both machines need to be using SQL Server 2005.
Each computer has one set of auxiliary files (writing system files, fonts, keyboards, and encoding
converters), shared by all projects on that computer. These files are only accessed by that
specific computer. If you open a project on another computer, FieldWorks attempts to use the
auxiliary files on the computer where it is running (that is, the local computer). If the two
computers do not have a similar set of auxiliary files, you might get unexpected results.
External links might fail when you access a FieldWorks project from another computer. For
information about how to avoid this in Data Notebook, search for Project Properties, External
Links tab in the online Help for any FieldWorks application.

Ethnologue codes
The built-in Ethnologue database that comes with FieldWorks, which enables you to select the
Ethnologue code for the language you are working with, has been upgraded to the 16th edition.
Some Ethnologue codes have been changed since the last version of the Ethnologue. If the code
for your language has changed, you will find that FieldWorks no longer knows the Ethnologue
code for the language. To correct this omission, in FieldWorks Project Properties, Writing
Systems tab, select a writing system for the language, then click Modify. Click the ellipsis
button displayed next to the label Ethnologue code, and find the language in the Ethnologue
list.

Firewall
For you and your colleagues to open each other’s FieldWorks projects across a network, you
need to allow SQL Server to be exempt from the Windows Firewall.

e5f46ed4-1fbd-4681-8f48-c699fea09843.rtf Edited on 7/3/2012 8:02:00 PM
FieldWorks 6.0 ReadMe 13

To do this or to check whether it is already exempt, open Control Panel…Windows Firewall.
Click the Exceptions tab. If sqlservr.exe is not in the Programs and Services list, click Add
Program. Browse to the C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn
folder*, and then select sqlservr.exe. Click OK. SQL server is added to the list of exceptions.
Click OK. You need to exempt sqlbrowser.exe as well. This is in the C:\Program Files\Microsoft
SQL Server\90\Shared directory.
*If you have other applications that use MS SQL Server, you will have more than one MSSQL.?
folder. Use the one which contains the file perf-SILFWsqlctr.ini in the Binn folder.

Program stops responding
If a FieldWorks application stops responding, it is typically because SQL Server is busy working
in the database. You might need to wait until the FieldWorks application can start responding
again.
1. At the far right of the taskbar, right-click the notification area, and then click Task Manager.
The Task Manager window appears.
2. Click the Processes tab, and then look for the following:
 When sqlservr.exe uses most of the CPU time, it is busy working in the database.
 When a FieldWorks process uses some of the CPU time, the application might start
responding again. (Flex.exe is Language Explorer, FwNotebook.exe is Data Notebook,
and FwListEditor.exe is Topics List Editor).
3. Close the Task Manager window.

Restore – password memory jog is missing
If you attempt to restore a backup that was locked with a password, the Enter Password dialog
box will not display the memory jog that you may have entered when you configured the backup
password.

Writing systems (InstallLanguage Message)
The InstallLanguage Message dialog box appears in the following three scenarios. The
information in the first paragraph on the dialog box depends on the scenario.

e5f46ed4-1fbd-4681-8f48-c699fea09843.rtf Edited on 7/3/2012 8:02:00 PM
FieldWorks 6.0 ReadMe 14

 Scenario 1: You start a FieldWorks application for the first time after installing FieldWorks
(or upgrading to a newer version) and other FieldWorks applications are already running. For
example, you start Language Explorer and Data Notebook is already running.
 Scenario 2: You add (define) a new writing system or modify an existing writing system in
one FieldWorks application and other FieldWorks applications are also running. For
example, you add a writing system in Data Notebook and Language Explorer is also running.
 Scenario 3: You add (define) a new writing system or modify an existing writing system, but
no other FieldWorks applications are running.

e5f46ed4-1fbd-4681-8f48-c699fea09843.rtf Edited on 7/3/2012 8:02:00 PM
FieldWorks 6.0 ReadMe 15

Solution for Scenario 1 and Scenario 2
1. Close the other FieldWorks application windows.
2. If you are aware of any other programs that use International Components for Unicode
(ICU), close them. For example, the Clipboard Converter program.
3. On the InstallLanguage Message dialog box, click Retry . You might need to click Retry
more than once.
If the dialog box appears again even after you close the programs, see the following solution.

Solution for Scenario 3
1. On the InstallLanguage Message dialog box, click Cancel.
The writing system appears to be added or modified in FieldWorks, but it is not added or
modified in International Components for Unicode (ICU). For example, the sort order may
not work correctly.
2. Exit the FieldWorks application, and then start it again.
3. On the File menu, point to Project Management, and then click FieldWorks Project
Properties.
The FieldWorks Project Properties dialog box appears.
4. Click the Writing Systems tab.
5. Select the writing system, and then click Modify.
The Writing System Properties dialog box appears.
6. In the Abbreviation box, edit the writing system abbreviation.
7. Click OK.
8. Click OK.
The writing system is added or modified in International Components for Unicode (ICU).
9. To return the writing system abbreviation to its original value, go to step 3.

Writing systems (limitations in FieldWorks 6.0)
 To avoid confusion, enter a unique abbreviation for each writing system. If you add a second
writing system for a language, type a few characters at the end of the abbreviation to identify
the writing system. For example, Sen for Sena orthographic and Sen_I for Sena (IPA)
writing systems.
 Single-reference fields (for example, Status, Confidence, Event Type, and Place of Birth)
do not support Graphite rendering, but do support Uniscribe rendering.
 Drop-down lists (for example, the Status and Confidence fields and List Item and
Keyword in the List Chooser) do not support Graphite rendering, but do support Uniscribe
rendering. However, they only display a single font. If there are multiple languages, some
data might not be readable.

e5f46ed4-1fbd-4681-8f48-c699fea09843.rtf Edited on 7/3/2012 8:02:00 PM
FieldWorks 6.0 ReadMe 16

 In Topics List Editor, the Chooser dialog box and the List Items pane support Graphite
rendering, but do not allow multiple heights for items. If items have different heights, some
might not be fully displayed.
 FieldWorks supports left-to-right and right-to-left scripts.
 If you paste text containing multiple languages from a non-FieldWorks application into a
FieldWorks application, FieldWorks does not apply the writing systems that correspond to
the languages. It might display boxes, instead of the correct characters. In certain situations
(probably involving scripts with complex rendering), FieldWorks might stop responding
because the UniScribe processor fails to render the characters.
Solution: Always select the correct writing system in FieldWorks before you paste text from
a non-FieldWorks application. Paste text from only one language at a time.
 We recommend that you use only Roman characters in style names. If you use diacritics or
complex scripts in style names, any of the following problems might occur:
 FieldWorks displays incorrectly formatted text, because it applies styles incorrectly.
 The active FieldWorks application stops responding.
 The active FieldWorks project becomes unusable.

Writing systems (modifying a writing system or opening a project)
If the following message appears when you modify a writing system, or open a FieldWorks
project for the first time on a computer, try the following solutions, in order.
The writing system could not be modified. There is a problem in your language definition.
See the FieldWorks ReadMe for help in this area.

 Solution 1: For major languages, FieldWorks expects a two-letter code, instead of a three-
letter code for the language. (The two letter code for a language can be seen in the Internal
Writing System code section of the Writing Systems Properties dialog in the General
tab.) To make sure FieldWorks uses the equivalent two-letter code: On the General tab of
the Writing System Properties dialog box, click the ... button. Search for the language,
select the standard code, and then click OK. FieldWorks will automatically convert the
Ethnologue code into the appropriate two-letter code.
 Solution 2: Exit FieldWorks, move the .xml file for the writing system from the Languages
subfolder of the Application Data\SIL\FieldWorks\Languages folder to another folder, and
then start FieldWorks. FieldWorks creates a new .xml file for the writing system using the
properties from the project.

e5f46ed4-1fbd-4681-8f48-c699fea09843.rtf Edited on 7/3/2012 8:02:00 PM
FieldWorks 6.0 ReadMe 17

Removing (uninstalling) FieldWorks
If you remove FieldWorks, the FieldWorks installer deletes only unmodified files that it put in
the SIL\FieldWorks folder during installation.
FieldWorks does not delete the following:
 Files that FieldWorks installed, if you modified them (for example, writing systems)
Exception: FieldWorks deletes the Lela-Teli and Sena projects, even if you modified them.
 Files that you created in, moved to, or copied into any FieldWorks folders (for example,
projects, writing systems, and pictures)

Note: In the Currently installed programs list on the Add or Remove Programs window,
FieldWorks appears as SIL FieldWorks.
After you remove FieldWorks, the extra software automatically installed by the Master Installer
is still installed. You can remove many of these programs, for example SQL Server.
1. On the Control Panel window, double-click Add or Remove Programs.
The Add or Remove Programs window appears.
2. In the list, select Microsoft SQL Server 2005.
3. Click Remove.
The Component Selection screen appears.
4. Select the SILFW instance and Click Next then Finish.
Other instances of SQL Server might appear in the list, but only FieldWorks applications use the
SILFW instance. If there are no other instances and you are sure no other programs use SQL
Server, you can also uninstall Microsoft SQL Server Native Client, Microsoft SQL Server Setup
Support Files, and Microsoft SQL Server VSS Writer in Add or Remove Programs.
Caution: Do not delete the c:\Program Files\FieldWorks\MSSQL$SILFW subfolder if SQL
Server 2005 is installed. This folder was installed by older versions of SQL Server and unless
you specifically uninstalled the older version, when SQL Server 2005 installed, it simply
upgraded the files in this folder rather than installing the new files under c:\Program
Files\Microsoft SQL Server.

Caution: Remove a program only if you are sure it will not affect any remaining programs on
your computer. For example, we recommend that you do not remove Microsoft Internet
Explorer, even if the Master Installer installed it.

Problem in Sorting tab of Writing System Properties
In FieldWorks 6.0 the Load from button in the Sorting tab of the Writing System Properties
dialog does not work. You can still cut and paste sorting specs from another writing system. If
you need to get a copy of the sorting information from a built-in writing system, go to
http://demo.icu-project.org/icu-bin/locexp, pick the locale, go to the Collation rules section, click the

e5f46ed4-1fbd-4681-8f48-c699fea09843.rtf Edited on 7/3/2012 8:02:00 PM
FieldWorks 6.0 ReadMe 18

Demo button, then click Fetch rules for locale. The Custom Rules window provides a copy of
the rules that can be cut and pasted into FieldWorks.

Potential issues
Cannot start FieldWorks
In the very unlikely event that your project is corrupted, FieldWorks might fail to start. If this
happens, start the FieldWorks application again. A special dialog box appears. You can open a
different project or restore the corrupted project from a backup file.
If nothing appears to happen when you start a FieldWorks application, and no error message
appears, do the following:
1. At the far right of the taskbar, right-click the notification area, and then click Task Manager.
The Task Manager window appears.
2. Click the Applications tab, look for the FieldWorks application under Task, and then do one
of the following:
 If the application is in the list on the Applications tab, select the application, and then
click Switch To, to bring the application to the front.
 If the application is not in the list, click the Processes tab, and then look for the process
that runs the application in the Image Name column. (Flex.exe is Language Explorer,
FwNotebook.exe is Data Notebook, and FwListEditor.exe is Topics List Editor).
If the process is in the list on the Processes tab, but the corresponding application is not
in the list on the Applications tab, select the process, and then click End Process.
3. Close the Task Manager window.
4. Start the FieldWorks application again.

Keyman not functioning correctly
Keyman uses a keyboard hook from Microsoft Windows to intercept keystrokes. If another
program gets a keyboard hook before Keyman, it prevents Keyman from getting the keyboard
input. In this case, even though Keyman is loaded, it cannot convert your keystrokes properly.
You might see this in the system language bar as No Keyman Keyboard, even though the
keyboard is correctly installed, and FieldWorks is configured to use the Keyman keyboard.
If you start Keyman manually and you encounter this problem, set Keyman to start automatically
when you restart your computer. In some situations this will solve the problem, since Keyman
can obtain the keyboard hook before the other program. Do the following:
1. On the Start menu, point to All Programs, and then point to Tavultesoft Keyman.
2. Click Keyman Configuration.
3. Click Options.
4. Select the Start Keyman with Windows check box.

e5f46ed4-1fbd-4681-8f48-c699fea09843.rtf Edited on 7/3/2012 8:02:00 PM
FieldWorks 6.0 ReadMe 19

If this solution does not work, or is undesirable, identify the other program and disable it. This
involves a fair amount of computer expertise. Here are three places to look for other programs
that could cause the conflict:
 Programs installed in your Start Menu\Programs\Startup folder.
 In the registry under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
 In the registry under
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
Tip: You can remove programs from the Startup folder, or add -- (two hyphens) in front of
registry entries in the Run keys to disable them, and then restart Windows.

Typing gets ahead of display
When using Keyman 6.2, FieldWorks has a problem when using some Keyman tables with TSF.
The combination of Keyman 6.2 and TSF causes keyboard input to be sluggish. If your typing
gets ahead of the display, FieldWorks attempts to display all of the characters since the last
display update. However, when this happens, it can cause Keyman to miss changing some
keystrokes, or even reorder the characters, putting changed characters ahead of unchanged
characters. This can be especially troublesome if you type fast or if your computer is slow. A
special fix to the Keyman keyboard can be made to solve this problem. This problem occurred
with the old IPA keyboard (ipaUni10.kmx). If you encounter this problem and are using this
older keyboard, switch to the newer IPAUni11.kmp keyboard included with this installation.
(Look in C:\Program Files\SIL\FieldWorks\Keyboards\IPA\Keyman.)

Drawing error: Error in initializing Graphite font
The following error message might indicate that a writing system has a default font, which is
now uninstalled.
Drawing error: Error in initializing Graphite font “[font name]” -- could not load Silf table
for Graphite rendering.
Possible solutions:
 Install the font.
 On the Attributes tab of the Writing System Properties dialog box, select the default fonts.
(It is possible that an internal error occurred, even though it appears you selected the fonts.)
 On the Writing Systems tab of the FieldWorks Project Properties dialog box, hide any
writing systems from the active project that are not in use, or not needed anymore.

Program stops responding
There is a remote possibility that a FieldWorks program might stop responding when you
simultaneously use multiple FieldWorks programs (for example, Data Notebook and Topics
List Editor). If this occurs, save your changes in the program where you first made the change.
Example: You open the Topics Lists dialog box in Data Notebook, and use it to open a topics
list in Topics List Editor. While the Topics Lists dialog box is open, you also open the Topics

e5f46ed4-1fbd-4681-8f48-c699fea09843.rtf Edited on 7/3/2012 8:02:00 PM
FieldWorks 6.0 ReadMe 20

List Properties dialog box in Topics List Editor, and then change the name of the active topics
list, close the Topics List Properties dialog box, but do not save your changes. When you select
and try to rename the same list on the Topics Lists dialog box in Data Notebook, the program
stops responding, because it is trying to change information which is locked in the database. To
solve this, on the File menu in Topics List Editor, click Save.

Scheduled tasks fail to start
The FieldWorks backup system uses the Windows Task Scheduler to manage scheduled
backups. Users on connected network computers might experience a Task Scheduler problem
affecting all tasks, including scheduled backups of FieldWorks. This problem appears as tasks
that fail to start.
In the Task Scheduler log file, you find a problem with the user’s logon name or password. The
task completes successfully, if the password is re-entered each time the task fails. This gives the
impression the Task Scheduler is failing to store the password, but this is not the case. If the
computer is on a network, it is likely caused by network settings.
Note: Only a network administrator can change the following network settings.
1. Run the Active Directory Users and Computers Management Console.

2. Edit the properties for the domain containing the users who are experiencing the problem.

3. For each enabled domain group policy, edit the properties by doing the following: Navigate
to User Rights Assignment, and then Set Log on as a batch job to Not defined.
Note: The name of your domain group policy might be different from the preceding picture. For
example, the policy might be the Default Domain Policy, rather than the Default Domain
Controllers Policy.
The following picture shows the default setting. All users have the right to log on as a batch job.

e5f46ed4-1fbd-4681-8f48-c699fea09843.rtf Edited on 7/3/2012 8:02:00 PM
FieldWorks 6.0 ReadMe 21

If the problem continues, install all available service packs and patches for Microsoft Windows.
On the Web, go to http://www.microsoft.com/

Technical support
FieldWorks is distributed as freeware. As such, no warranty or support is provided, and you use
it at your own risk. Because it is under active development, we welcome bug reports. However,
when you submit a bug report, we cannot guarantee that you will receive a reply or that the bug
will be fixed.
If you are part of a community of FieldWorks users, we encourage you to use your contacts
within that community to obtain support and training. We also encourage you to visit the
FieldWorks Web site: http://www.sil.org/computing/fieldworks/
For technical information on the Web, go to http://fieldworks.sil.org/

Acknowledgements
FieldWorks includes the following software:
 DotNetBar (http://www.devcomponents.com/dotnetbar/)
 expat - XML Parser Toolkit (http://www.jclark.com/xml/expatfaq.html)
 ICSharpCode (http://www.icsharpcode.net/OpenSource/SD/)
 International Components for Unicode (http://www-
306.ibm.com/software/globalization/icu/index.jsp)
 SIL software: CC, TECkit, SilEncConverters, XAmple (http://www.sil.org/computing/)
 Skybound Software (http://www.skybound.ca)
 #ziplib by SharpZipLib (http://www.icsharpcode.net/OpenSource/SharpZipLib/)
 Xceed Zip (http://www.xceedsoft.com/)
FieldWorks depends on:
 SQL Server 2005 Express Edition
(http://www.microsoft.com/sql/editions/express/default.mspx)

e5f46ed4-1fbd-4681-8f48-c699fea09843.rtf Edited on 7/3/2012 8:02:00 PM