FLExLIFTInfo
FLEx V1.1 will include export to a best-we-could-do-at-the-time form of LIFT. Hopefully we'll get a respectable version in there for the next version . In the meantime, this version allows you to get FLEx data into WeSay.
[edit]
FLEx v1.? Export to LIFT Errata
These are for lifts with bear the producer value "SIL.FLEx.V1Pt2".
- Empty <def/>'s and <gloss/>'s are no longer exported when these fields are empty.
[edit]
FLEx v1.1 Export to LIFT Errata
These are for lifts with bear the producer value "SIL.FLEx.V1Pt1".
- Before exporting, set your primary analysis language to English (or any other language which the semantic domains contain abbreviations in). Otherwise, Semantic Domains values will not be exported correctly.
- Only the following fields are exported:
- LexemeForm
- Sense
- Gloss
- Definition
- Grammatical Info Abbreviation
- Semantic Domain abbreviations
- Example Sentences
- Translations
- Empty <def/>'s and <gloss/>'s are in exported when these fields are empty.
- Strings that may have text in multiple languages (e.g. example) are exported as simple Unicode strings, not proper LIFT <span>'s.
- The following are known places where these files deviate from the existing LIFT specification:
- use of "ws='en'" rather than LIFT's "lang='en'".
- use of FW's notion of a "Writing System", which combines language and script. LIFT wants these to be separate.
- range sets are not used for Parts Of Speech
- range sets are not used for Semantic Domains
[edit]
Importing back into FLEx
TODO: update the situation on how to *import* LIFT into FLEx.
