fatty- / daisy-pipeline

Automatically exported from code.google.com/p/daisy-pipeline
0 stars 0 forks source link

Feature request: ignore audio files #298

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
When collecting test data from users for debugging, the file set can be very 
large and cumbersome to send back and forth. 

It would be helpful if some scripts, such as DAISY 202 to EPUB 3 and DAISY 3 to 
EPUB 3, could ignore audio files so the user could submit just the text 
portions (HTML, Ncc, OPF, etc) of their books.

This would allow for easier initial testing, without having to wait for a 600MB 
book to be sent.

Right now when I run daisy202-to-epub3 on a book with the audio files missing, 
I get file copy errors at the end of the process. I don't know if this is 
expected behavior or not (perhaps related to #297).

Original issue reported on code.google.com by marisa.d...@gmail.com on 23 Apr 2013 at 8:20

GoogleCodeExporter commented 9 years ago
What if we throw warnings instead of errors when files are not found?

- The file copy errors are probably not caught at the moment so first of all we 
should handle the FileNotFound errors in XProc using p:try/p:catch.
- px:fileset-copy / px:fileset-store  / etc. could possibly have a 
"fail-on-missing-file" option to decide if warnings or errors should be thrown

Related issue:
issue 242 - Add support for logging levels to the XProc message step

Original comment by josteinaj@gmail.com on 23 Apr 2013 at 9:09

GoogleCodeExporter commented 9 years ago
Oh that would be a useful option, to throw warnings instead of errors. The 
option needs to be controllable at the top level, in addition to the 
convenience of having px:fileset-* operations handle it internally.

Original comment by marisa.d...@gmail.com on 25 Apr 2013 at 5:23

GoogleCodeExporter commented 9 years ago
DAISY 2.02 to EPUB 3 has a "mediaoverlays" option to enable/disable MO 
production. If it is set to "false", MO are not produce and audio files should 
be ignored.

Would that work ?

I otherwise agree about the changes suggested  above to improve error handling 
/ logging level.

Original comment by rdeltour@gmail.com on 7 May 2013 at 11:53

GoogleCodeExporter commented 9 years ago

Original comment by marisa.d...@gmail.com on 2 Jul 2013 at 12:36