Each file ripped is displayed in the log file with the full path on the machine
on which the rip is performed, although the log itself is generally
automatically stored in the same path as the ripped file.
It would be nice to be able to generate a log file that would only display a
relative path (to the location where the rip is saved, for example) or only the
file name of the ripped file (therefore in a way relative to the log file
location)
This would make the log file more "independent" of the location where the file
are stored, and avoid displaying unnecessary or personnal information, such as
the user name (when the file is stored in a user profile document area).
Then a log checksum could be implemented to guarantee the log is not forged,
like in other ripping softwares (but that is another story).
Original issue reported on code.google.com by eric.boc...@gmail.com on 23 Sep 2011 at 7:10
Original issue reported on code.google.com by
eric.boc...@gmail.com
on 23 Sep 2011 at 7:10