Thanks. : )
quick question....
Code:
Usage: xraybuilder [-o path] [--offset N] [-p] [-r] [-s shelfariURL] [--spoilers] [-u path] mobiPath
-o path (--outdir) Path defines the output directory
If not specified, uses ./out
--offset N Specifies an offset to be applied to every book location.
N must be a number (usually negative)
See README for more info
-p path (--python) Path must point to python.exe
If not specified, uses the command "python",
which requires the Python directory to be defined in
the PATH environment variable.
-r (--saveraw) Save raw book markup to the output directory
-s (--shelfari) Shelfari URL
If not specified, there will be a prompt asking for it
--spoilers Use descriptions that contain spoilers
Default behaviour is to use spoiler-free descriptions.
-u path (--unpack) Path must point to mobi_unpack.py
If not specified, searches in the current directory
After used once, mobi2mobi and mobi_unpack paths will be saved as default and are not necessary to include every time.
You can also drag and drop a number of mobi files onto the exe after those paths have been saved.
Books must be DRM-free. If you create an X-Ray file for a book, but still use the DRM copy on your Kindle,
you will run into issues. The X-Ray has to be used with the DRM-free version it was created from.
is the usage outdated now. I see it has changed a bit (I think)
much obliged