View Single Post
Old 04-18-2014, 05:44 PM   #32
skreutzer
Software Developer
skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.
 
skreutzer's Avatar
 
Posts: 190
Karma: 89000
Join Date: Jan 2014
Location: Germany
Device: PocketBook Touch Lux 3
No, of course I've haven't read the specification in its entirety, but you will well know that there is much less room for interpretation regarding structure than it is for rendering, and that a lot of statements are made to specify what's actually valid structure, and that there's even a validator implementation available from the IDPF, and after all this - the room left for interpretation regarding structure is neither common in real-world cases nor trivial, or needs to be fixed in the future. On the other hand, without doubt, invalid constructs can be detected, too. And on the readers side, as already mentioned, developers have to expect worst case scenarios for the input files, on the EPUB creation tool side, developers have to expect the worst case scenarios for readers of their output file instead of actually really causing those worst case scenarios by themselves and leave the mess up to the user/reader who can't help himself.
skreutzer is offline   Reply With Quote