Recent Forum Comments

  • (Tobi forum) 1 hour 33 min ago

    Excellent

  • (Tobi forum) 1 month 6 days ago

    Follow-up:

    Internal alpha testing (aka preview build) is complete.

    Tobi version 2.6.1.2 is now available for public testing (beta build).

    Further information about this release is available at the following link:

    http://www.daisy.org/tobi/tobi-2.6.1.2-beta

  • (Pipeline forum) 1 month 2 weeks ago
    Hi V. Without more context, I assume you're trying the "Audio Tagger" script of the DAISY Pipeline 1. The command line documentation combined with the documentation of the Audio Tagger script should help you find the proper command line. For instance:
    
    $ ./pipeline.sh scripts/modify_improve/multiformat/AudioTagger.taskScript --audioTaggerInputFile=/Users/V/dtb/ncc.html --audioTaggerOutputPath=/Users/V/out/
    
    Hope this helps, Romain.
  • (Pipeline 2 forum) 1 month 3 weeks ago

    This is being further discussed on the daisy-pipeline-dev mailing list.

  • (Pipeline 2 forum) 1 month 3 weeks ago

    Thanks for letting us know the solution. Was Java installed beforehand or during the installation of Pipeline 2?

  • (Obi forum) 1 month 3 weeks ago

    Hello Eric,

    Thanks for mailing us.

    Let's have an example, consider a book structure like this:

    Heading h1 (with audio)
    Heading h2 (empty section)
    Heading h3 (with audio)

    If i export it , there wont be any error, the export file will look like this:

    Heading h1 (with audio)
    Heading h3 (with audio)

    Empty section(h2) wont be exported.Here the order of hierarchy is wrong so when you import this file in obi, an exception is thrown.On pressing OK button in exception messagebox, Obi will work fine without any error.

    Note: It is recommended not to export project with empty section.

    Hope i have clarified your issue.
    If you want to send us any of the NCC/OPF file and images, please mail us at obi.feedback@gmail.com .

    With Regards
    Rachana

  • (Obi forum) 1 month 3 weeks ago
    You can export custom metadata in DAISY 3.0 export but not in DAISY 2.02. It is restricted. We can allow it in future if there is strong use case for it.
    In case you really want to work on advancements, it is better to migrate to DAISY 3 or EPUB 3.
    With regards
    Avneesh
  • (Obi forum) 1 month 3 weeks ago

    Thanks Avneesh for your reply. Just for me to be sure I understand: could you tell me if OBI allows the creation of new (customized) metadata or not ?
    I created 3 new metadata name in OBI 4.0 alpha: DC:ISBN and NCC:ISBN and DTB:ISBN, each time with a value (like 978-123-010 or so). I used the 'Personnalisé' metadata view (the
    last name). I receive no error at creation, no error at export DAISY 2.02 and no error running the Validator DAISY 2.02 (error display on screen or in a file).

    Regards

    P.S I will send you a screen capture in a mail of what I did in OBI so that you better see

  • (Obi forum) 1 month 4 weeks ago

    Hi Eric,

    Right now Obi's DAISY 2.02 export uses default scheme. It was done to keep it simple for end users.
    We will see how we can extend metadata user interface for adding scheme while maintaining its simplicity. However it would not be possible in up coming Obi 4.0 release, because it requires UI refactoring. I am adding it to the list of feature requests.

    With regards
    Avneesh

  • (Obi forum) 1 month 4 weeks ago

    Hi Eric,

    I think that validator may be throwing error after your addition of dc:isbn in the book. The scheme attribute is the right way.

    With regards
    Avneesh