Am 03.12.2013 11:12, schrieb Henning Hraban Ramm:
Am 2013-12-03 um 14:42 schrieb Urs Liska <u...@openlilylib.org>:
Am 03.12.2013 09:35, schrieb Curt:
Collaboratively creating lilypond anki decks could be clunky. You'd probably
be collaboratively editing the generating scripts themselves, and then be
building the decks from that, and then reimporting on top of your already
existing deck, which could be problematic.
Hmmm.
In which form are decks and cards stored on disk with Anki?
A small file tree with several SQLite dbs:
Anki
├── Hraban
│ ├── backups
│ │ ├── backup-13.apkg
│ │ ├── backup-14.apkg
│ │ ├── backup-15.apkg
│ │ └── backup-42.apkg
│ ├── collection.anki2
│ ├── collection.log
│ ├── collection.media
│ ├── collection.media.db
│ └── deleted.txt
├── README.txt
├── addons
└── prefs.db
Thanks for that explanation. So Anki decks aren't really accessible to
version control, i.e. a Git repository.
AFAICS in order to maintain a deck collaboratively one would need a
server application that interacts with the SQLite dbs.
Which is of course feasible (I think SQLite support is nearly anywhere),
but would of course need considerable more effort than simply
initializing a repo.
OTOH I could imagine there already exist working approaches.
No time to research, though :-(
Urs
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
