Quote:
|
Originally Posted by Steve Jordan
Okay, I'm understanding better (apologies, I'm not a programmer). So, whose responsibility is it to create and update the secondary modules? If that is in the hands of the e-reader developers (as opposed to the authoring tool creators), that would seem to make sense to me.
|
Yes, that is the plan.
The important point to stress is that mastering is done into a strictly-defined markup allowing both push-button conversion plus styling using standardized style sheets. As soon as one allows any markup flexibility, everything gets loosey-goosey and we're back to square one again of tag abuse, and nothing fits with nothing.