List of forums • View recent posts • View recent comments • • Go to daisy.org

Pipeline 2.02 validator an standalone daisy 2.02 validator

Submitted by Gino Peenen on Mon, 2010-05-31 23:36

Pipeline

I've created a new project but no title in the format of word. Then "save as daisy" in an inport tobi. 've added audio to this project. Validated by tobi = ok. Validated in the pipeline = ok. Then downgrade to three Daisy daisy 202 = ok too. This output also validated with pipeline no errors no Waring. Then validated the same project with the standalone Daisy2.02 validator and it gives critical error. This is the result: error (critical) in e:\tests\sport3\_xuk\buiild\daisy202\content.html [1:153] : document does not validate against the DTD referenced in the document, Invalid at the top level of the document. ?xml version="1.0" encoding="utf-8"?> This happens even when I do a project in the pipeline : create and distribute / Daisy book / TTS narrator( daisy xml tot daisy book. If I validate this 2.02 output with the standalone daisy 2.02 validator I get the same error. What is right or wrong? We use the standalone daisy 2.02 validator always build it into MP3. I post this also on the pipeline forum. Best regards Gino

I've not heard of such a

Submitted by RDeltour on Tue, 2010-06-01 02:47.

I've not heard of such a problem before, but I can try and look at the issue. Can you please send me the DAISY 2.02 book via email or FTP ? My email is rdeltour (at-nospam) gmail (dot) com. Romain.

Thanks for the input

Submitted by RDeltour on Tue, 2010-06-01 05:53.

Thanks for the input files. The validation report is actually a limitation of the standalone 2.02 validator, who does not accept the XML prolog (<?xml ... ?>) and the Doctype declaration (<!DOCTYPE ...>) on the same line. The Pipeline 2.02 generator previously inserted line breaks around the doctype to work around this limitation, but a recent change in the code inadvertently reverted this safety behavior. I fixed it back in the code repository, it will be included in the next release. For now, the workaround is to either ignore the error (this is a "false positive"), or insert line breaks around the doctype declaration. Thanks for the report! Romain.

For the record, the

Submitted by RDeltour on Tue, 2010-06-01 06:14.

For the record, the limitation has been added to the list of know issues: http://code.google.com/p/daisytools/wiki/Daisy202ValidatorKnownIssues#._... Romain.