> Peter Bienstman wrote: > >> The main one being that anki > >> imports and renames image files that you may wish to use in your cards > >> and holds them in a flat folder structure. I don't want to do that. I > >> deliberately rename jpegs to have meaningful names and contain useful > >> exif data and resized to suit mnemosyne. I also use the same jpegs > >> linked to from an openoffice database I'm working on which simply links > >> to the same physical files. And sometimes I use the same jpeg in several > >> mnemosyne cards depending on my goals. > > > > Note that 2.0 currently makes a copy of your picture files and stores it > > in its own folder (it does not rename the files though, so they can still > > have meaningful names). > > > > The idea behind is that that makes it easier for users to backup their > > cards + media files if they are all in the same place. > > > > I'm open for discussion on this, though. > > Where does it store this folder and would it be user configurable?
No, that would complicate the UI. > How > would it cope with, say, several thousand images in one folder? That should not be an issue. They are in a single directory though, so if you want to have some hierarchy, it should be at the filename level (i.e. parent_child.png) instead of at the directory level (parent/child.png) > Backing up is easy. I use a wrapper script to invoke mnemosyne so I > don't forget, but basically it simply backs up the entire .mnemosyne > folder to another location If people store their media outside of the .mnemosyne directory, this procedure will not back up their media. Peter -- You received this message because you are subscribed to the Google Groups "mnemosyne-proj-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mnemosyne-proj-users?hl=.
