rusio / vokabeltrainer Goto Github PK

I tried to send you an email and got this error:

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of
its recipients. This is a permanent error. The following address(es)
failed:

[email protected]:
SMTP error from remote server for RCPT TO command, host: mx.sourceforge.net (216.34.181.68) reason: 550 unknown user

I guess your email is out of date. If you update it, I'll try resending the email.

Filenames

Vocabulary files are currently auto-detected only if they are both inside $VOCS_DIR and named vocabulary.xyz. How about assuming $VOCS_DIR is used solely for vocabulary data and assuming every file in that directory is vocabulary. This would allow for clear filenames.

Subdirectories

Adding support for subdirectories. The basic idea here is to (optionally) specify a directory rather than a file containing the vocabulary to be asked. VokabelTrainer would then load all files from that directory (and all subdirectories) and concentrate them for testing. This would allow for a well-ordered database similar to the following:

$VOCS_DIR/english
$VOCS_DIR/english/book1
$VOCS_DIR/english/book1/chapter1.txt
$VOCS_DIR/english/book1/chapter2.txt
$VOCS_DIR/english/book1/chapter3.txt
$VOCS_DIR/english/book2
$VOCS_DIR/english/book2/chapter1.txt
$VOCS_DIR/english/book2/chapter2.txt
$VOCS_DIR/english/book2/chapter3.txt

One could then e. g. choose to run vokabeltrainer english/book1 or vokabeltrainer english/book2/chapter1.txt or even vokabeltrainer english.

Stable file format

Not quite sure about how this is handled best. The data inside the files is often restructured dramatically, most drastically when lines move between stores. Comments are also lost in rewrites. The store could be included after the word itself (together with the date and such), making the list more stable and allowing for real comments which could be used to structure the file (similar to config files).

This:

===== Store: [newbies] =====
swim = schwimmen | 2017-03-04 | 2 | 0

===== Store: [pending] =====
make = machen | 2017-03-04 | 1 | 1
go = gehen, laufen | 2017-03-04 | 0 | 0

Becomes this:

# Movement
go = gehen, laufen | 2017-03-04 | 0 | 0 | pending
swim = schwimmen | 2017-03-04 | 2 | 0 | newbies

# Production
make = machen | 2017-03-04 | 1 | 1 | pending

For compatibility with existing data files one could either use some converter or include a legacy mode. The syntax used in a file would easily be determined by the presence or absence of store-headings.