Known Issues and Limitations

As with any piece of software, Language Forge has some known issues and limitations. We work hard to improve functionality and usability, but are unable to immediately address all known issues and limitations. For your reference, here are the known issues and limitations. Known issues and limitations may be addressed in the future. Some of the items below are labeled as anticipated to be addressed, or considered for being addressed.

Send/Receive

• Some types of FLEx custom lists will cause a project to go on hold in Language Forge. (See Issue 976 for more information.) [Anticipated]

FLEx Fields and Features not Available in LF

For all of the following, the easiest Workaround will likely be to view and edit them in FLEx. This information will be saved in your project, even though it is not presently visible in Language Forge.

• Main Entry
  • Morph Type
  • Complex forms
  • Components
  • Source Form (Called "Etymology" in LF): Only the vernacular field is supported- not the analysis fields.
• Senses
  • Lexical Relations [Anticipated]
  • Image's file path at the time of its upload (Although LF will still document the file path of images it uploads.)
  • Publish Picture In
• Variants [Considered]
• Allomorphs [Considered]
• Publication Settings [Considered]

Other

• An internet connection is required to use Language Forge [Anticipated]
  • Workaround: use FLEx to export your data for offline reference. Possibly to a PDF, or an app made with the Dictionary App Builder.
• Sign-in with Google does not work in the Language Forge app from the Play Store [Anticipated]
  • Workaround: Install Language Forge as a Progressive Web App from the browser instead. Here are instructions (external site)

Other Resources

Click here to see the Release Notes and learn how we have been improving Language Forge for you.