N – Nasals, generally (or only word finally).So I’ve set out four boolean settings (yes/no, True/False), which govern whether a given segment type is treated as a regular consonant, or separately from other C’s, in the syllable profile analysis: The question of segment interpretation has been an issue almost everywhere I’ve worked, and it is often a highly idiosyncratic (or language specific, as you like) thing. I Think I finished a new feature today, complete with a settings page for the user to make it work. But note that the interface isn’t as pretty (pay attention to the red circled area, not the long list of ?NoGlossOrDef? values…
If you have other gloss languages (like Hausa) in your LIFT database, you can elicit from those, too -so long as a lexeme-unit/form language isn’t also selected in the definition input languages. So to elicit in a language other then English or French, make sure that is in the lexeme-unit/form field in your lift database. If you don’t have a language selected that is actually in your lift database (the wordlist you are trying to fill out), you will get this errorː This “top-most”, critically, is the topmost language in the settings for the definition field, here: In the config tool under the SIL-CALW wordlist Task, it says: WeSay will use the top-most input system of the definition field to choose the prompting language (only English and French are available at this time). That is, the ‘en’ value here doesn’t do anything: WeSa圜onfig determine things, but not for the SIL Comparative African Wordlist (SILCAWL). I blogged before (a decade ago!) about adding new tasks to WeSay, and just today was setting up someone, and realized I’d missed documenting something.