When not to use Lute - jzohrab/lute GitHub Wiki
This documentation is deprecated/obsolete. Lute v2 has been replaced by Lute v3, a full Python rewrite. Please see the Lute v3 manual which includes notes on installation. If you have Lute v2, you can easily migrate to v3. Thank you!
As good as Lute is, it might not be for you. Below are some things that may lead you to decide to postpone using Lute for now:
| Item | Notes |
|---|---|
| Installation | Lute is not "shrinkwrap" software, yet. You have to install some components like PHP and Sqlite, or to use Docker. I've done my best to simplify the installation, and my ultimate goal is for a single-click install, but that's not ready yet. |
| Audio | Lute doesn't have an audio player. |
| Support "non-consecutive multiword terms" | Some languages, like German and Dutch, have terms that that split apart. For example, in German, the verb "einladen" can be split into "laden ... ein": "Ich lade dich zu meiner Party ein." I don't think any tool currently solves this well. See the notes at on this GitHub issue. |
| Flashcards/testing | Lute is designed for reading only, there is no testing. |
| Automated or bulk translation | Lute isn't designed to automatically create bidirectional readers, or to auto-create translations. You can use Lute's Term import feature, along with something like Google Sheets, to imitate that. |
There are other smaller features that Lute doesn't have yet (see the backlog), but the above are the biggest ones that may be dealbreakers for you.