Recent comments

The reauthorized Individuals with Disabilities Education Act (IDEA) was signed into law on Dec. 3, 2004, by President George W. Bush. As of that date the 1996 Chafee Amendment was also further revised.

“Specialized formats” was newly given the meaning in 2004 that it now "... includes large print formats when such materials are distributed exclusively for use by blind or other persons with disabilities." Large print was not previously mentioned as a "specialized Format".

The drafters of the revised Chafee statute in 2004 could have easily specifically mentioned DAISY as a "specialized format" at that tine. They did not. Where was the DAISY Consortium leadership?

Hi sreph45,

If you have no intentions of producing a full text - full audio book, Tobi would do the trick. What you will get is a book with headings (and possibly pagenumbers) and full audio.

- download OBI and install, read help manual, then start typing the headings for sections and chapters and import the appropriate audio (or the other way round...)
- download the DAISY Pipeline and install, then take exported Tobi book (the xml part which we like to call DTBook or DAISY xml) load it onto the pipeline and convert it to the format most appropriate to your purposes.

I would recommend Windows, but that only because I'm running it...and a lot of other task specific and non-DAISY software only lives there.

If you run into troubles contact me: daisym (at) tters.org

rgds
Olaf

Dear Herceg,

You can refer to the Command Line User Guide:
http://daisymfc.sourceforge.net/doc/enduser/cmd-user-guide.html

First you have to point the command to a "task script" file (with a *.taskScript extension). You can first use the "-i" option to get a list of the parameters to set, and then set this parameters using the "--name=value" syntax.

For instance, to get the information on the "DTBook to XHTML" script:
$ ./pipeline.bat -i scripts\create_distribute\xhtml\DtbookToXhtml.taskScript

Then to execute the conversion:
$ ./pipeline.bat scripts\create_distribute\xhtml\DtbookToXhtml.taskScript --input=C:\Input\dtbook.xml --output=C:\output\output.xhtml

HTH,
Romain.

I have a sample book which does not show the JPG image on my Tobi install. Where would you like me to send it to?

Hello Bonnie,

do you have page numbers in your converted document? If they are there and in the right place then it's a fault in your reading system. If there are no page numbers in your converted doc then see if these help:
http://www.daisy.org/forums/node/170
http://www.daisy.org/forums/node/137
http://www.daisy.org/forums/node/126

regards
Olaf

This is exactly whats happening on my PC using Windows 7.
Worked fine the day before - now nothing generates

Hi there,

I uploaded the project last week. Just want to make sure you received it.

Thanks,

Andrew

The implementation used for XML parsing and transformations are configured with the regular JAXP factory properties, in the pipeline.properties fle (notably javax.xml.transform.TransformerFactory, javax.xml.parsers.SAXParserFactory, and javax.xml.stream.XMLInputFactory).

If you want to use other factories in your transformer you can always temporarily set these system properties to something else at the beginning of the execution, then reset the old values after the execution.

If you use the built-in XSLTRunner tranformer, you can also set the transformer factory using the "factory" transformer parameter. See how it's done in one of the two aforementioned transformers.

HTH,
Romain.

Dear Tuomas,

1. Integrating XSLT-based transformations

It should be fairly straightforward to integrate an XSLT-based conversion as a Pipeline transformer. The Pipeline has built-in functionality to even create such transformer without writing Java code.

You can find more information on the Pipeline developer documentation:
http://daisymfc.sourceforge.net/doc/developer/transformer-authoring-guide.html
http://daisymfc.sourceforge.net/doc/index-developer.html

Note that the Pipeline uses Michel Kay's Saxon to run XSLT transformations. Saxon is an XSLT 2.0 and XPath 2.0 implementation but is also able to execute most XSLT 1.0 stylesheets.

For an example of a pure XSLT transformer, see the se_tpb_dtbook2latex (using XSLT 2.0)
http://daisymfc.svn.sourceforge.net/viewvc/daisymfc/trunk/dmfc/transformers/se_tpb_dtbook2latex/dtbook2latex.tdf?view=ma...

Or the dk_dbb_dtbook2rtf transformer (using XSLT 1.0)
http://daisymfc.svn.sourceforge.net/viewvc/daisymfc/trunk/dmfc/transformers/dk_dbb_dtbook2rtf/transformer.tdf?view=markup

Finally, note that you do not have to develop an Eclipse plugin or write an extension point to create a new Pipeline transformer. These concepts belong to the Eclipse RCP framework which is only used for the GUI layer of the Pipeline application.

2. Pipeline accessibility

Yes the Pipeline GUI should be out-of-the-box accessible to visually impaired users on Windows, Linux and Mac OS X. The underlying Eclipse RCP and SWT libraries are using the IAccessible2 API to call the native accessibility layers.
See also the Pipeline FAQ section on accessibility:
http://daisymfc.sourceforge.net/faq.html#access

3. Further developments

The Pipeline project is now in maintenance mode. It means that the DAISY Consortium will not allocate new resources to further develop it, but will however keep on supporting and helping third-party contributors.

As for future directions, we're about to officially launch the Pipeline 2 project, which is a fundamental redesign of the Pipeline framework to embrace new technologies and standards (notably W3C's XProc) and better integrate with the DAISY community and publishing mainstream.

You'll find more information on the Pipeline 2 development site:
http://code.google.com/p/daisy-pipeline/
http://code.google.com/p/daisy-pipeline/wiki/ProjectCharter

HTH,
Romain.

thanks for your help!!

Thanks Marisa turning off ZoomText sorted out the problem for me. I'd spent ages trying to fix this and didn't realise doing something so simple as that would fix the problem but I'm glad it did so thanks.