Collect Words in French, not all domains in French for a team

[Bep Langhout]

We are having a word collection workshop. One of the teams had an old database with words in semantic domains. I did an update for Fieldworks 9.2 (complete), but somehow their Semantic domain list and the questions are old and incomplete. Domain 2 is Une personne instead of La personne. Body only has an english name (body) while the French one (Corps) is lacking.

Is there a way to update the Collect words Semantic Domain questionaire on Fieldworks?

Thanks,

Bep

[Bruce Cox]

Hi Bep,

I've never had to do that, but information on this page looks like it could be helpful: Localizations - FieldWorks.

Cheers, bruce

--
"FLEx list" messages are public. Only members can post.
flex_d...@sil.org
http://groups.google.com/group/flex-list.
---
You received this message because you are subscribed to the Google Groups "FLEx list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to flex-list+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/flex-list/e399ec64-0d90-4e3d-ac1b-e00ef4d04396n%40googlegroups.com.

[Bep Langhout]

Their Semantic domains are messed up. Questions for the Eye are in the domain for Nose, for instance.

Changing the list, and then doing Send/Receive does actually include the list with Semantic Domains.

On one computer you can have a correct project (a different one) with all the Semantic Domains and Questions in French, and on the same computer their projects Semantic domain list is messed up.

[Kevin Warfel]

By way of explanation to everyone subscribed here, and for future reference to those who look for help on this topic in times to come, it is important to understand several things with regard to translated material in the FLEx User Interface:

1) These translations are referred to as "localized strings".

2) Localized strings are divided into two groups

   - those in lists (in the List area in FLEx) and 

   - those used in menus, dialog boxes, and other parts of the User Interface (UI). 

3) Both groups are currently updated and maintained in CrowdIn, but there are separate processes for incorporating updated strings from each group in a FLEx project.

4) Localized strings used in menus, dialog boxes, etc. are updated automatically for all projects when the user installs a new version of FLEx.

5) Updates to the localized strings in lists are done in two ways following the installation of a new version of FLEx.

   - in a newly created project, the up-to-date list is included automatically

   - in an existing project, 

        - updated lists are imported automatically for any Writing System (WS) that the user adds

        - updated lists must be imported for any pre-existing WS

As Bruce Cox pointed out, the page Localizations - FieldWorks includes instructions for the importation of updated list material. The Semantic Domains list is part of this, so it does not update automatically when FLEx itself is updated to a new version. That said, it is also important to realize that the version of the list(s) is dependent on the version of FieldWorks that is installed, so in order to be able to import the most up-to-date version of the lists, a version of FW must be installed that includes that up-to-date version of the lists.

In case it is helpful to anyone, here is an edited version of those instructions:

In FieldWorks 8 or later, when a writing system is added to a project, localized translated list content for that writing system will be installed automatically. If you need to update translations for a writing system already in your project, you would use a procedure similar to the one described below. Assuming a 64-bit version of Windows, and a default installation, the file you would choose would be c:\Program Files (x86)\SILFieldWorks 8\Templates\LocalizedLists-??.zip. Note that you are importing a zip file rather than xml.

1. Start FieldWorks.
2. Open the project you want to update the translated lists in.
3. Go to the Lexicon Area.
4. Choose the option File/Import/Translated List Content.
5. Navigate to c:\Program Files\SIL\FieldWorks9\Templates. Choose the file LocalizedLists-??.xml (where ?? is replaced by your language code). Click Open.
6. In Format/Set up Analysis Writing Systems, make sure your language is added as an Analysis Writing System.
7. Now go to the Lists area. Depending on what was in the language pack, you may see semantic domains in that language, or other lists (such as Morpheme Type). However, not all list content is translated in all languages.

Depending on a user's individual machine and setup, the portions I've highlighted in yellow may be different. On my laptop, I find the relevant files under c:\Program Files, not c:\Program Files (x86), as the instructions seem to indicate I should expect with 64-bit Windows.

One final detail that trips people up sometimes: The code that is chosen for a WS when it's added to a FLEx project is important. The localized lists are, for the most part at least, coded as macrolanguages. That is, they have a two-letter language code rather than a 3-letter code that corresponds to a specific dialect of the language. For example, "es" is the 2-letter code for Spanish. If a user adds a WS for Spanish but uses the 3-letter code "spq", the localized lists for "es" will not show up in the project. 

Hoping that's helpful,

Kevin

[Bep Langhout]

Wonderful!!! It worked!

[Kevin Warfel]

That's very good to hear, Bep!

To view this discussion visit https://groups.google.com/d/msgid/flex-list/d4074e1b-71cc-4b5c-86e0-16f629867345n%40googlegroups.com.

[Bep Langhout]

Except that the Send/Receive fails after that :-/

[Kevin Warfel]

Would this be an acceptable solution to the S/R problem?

Assuming that the data in Lexbox is correct,

Delete the FLEx project from the machine that is unable to S/R. (Note: Any work done on that machine since the last successful S/R will be lost.)

On the affected machine, use the Get a Project from a Colleague option to create the project again.

Best wishes,

Kevin

To view this discussion visit https://groups.google.com/d/msgid/flex-list/08fc250c-b35c-4172-9fee-b60b8a13fdf5n%40googlegroups.com.

[Ron Moe]

I don't know if this will help or not. I spent many years developing the list of semantic domains. I released six versions of the "Dictionary Development Plan" domains. I forget which version was first incorporated into FLEx. Somewhere along the line I was informed that the list of domains had become an "international standard" due to the number of people and software using it from many countries and languages. Because of this the development was frozen with version five. I spent a lot of time improving things for version six, but it was never integrated into FLEx. Each time I released a new version I prepared a conversion table which mapped which domains had been renumbered. I still have the conversion tables. However the software world has changed so much that I can no longer use a lot of my old files. One of the FLEx programmers could probably update the semantic domain assignments in a dictionary. You would need to know which version of the semantic domains was originally used to collect the words. But it might be easier in the long run to simply do it manually.

Ron Moe

To view this discussion visit https://groups.google.com/d/msgid/flex-list/CAHs8okXiwToEAwChKj5%2B5KoB9qe0iyNF0WDPrKbLNfJ-rYV92g%40mail.gmail.com.