Re: DP's "internal markup" (was Re: why the plain-text format is t
jim said:
Just to state the obvious, it sure would be cool if the work could be saved somewhere at that point in time when the work is still "reversible"
and, just to restate what has already been stated directly, you can save the work at almost any time in the workflow. but what you will find is that the text isn't all that valuable at most points in the workflow, because it contains errors, not to mention that obtrusive and awkward "d.p. markup"... even worse is that -- in order to justify their existence -- many proofers have taken to cluttering the text with "notes" that point out errors, instead of just fixing the darn things. (this means everything gets thrown on the postprocessor, so -- surprise, surprise -- postprocessing is now blocked up.) the text is at its peak once the errors have been eliminated, right before the linebreaks and pagebreaks are discarded, so it would be great if it could be archived in _that_ state... of course, it'd be even better if linebreaks and pagebreaks were to be actually carried over into the posted p.g. e-texts -- in such a way that they could be conveniently eliminated by anyone who wanted to do that, of course -- but i've been advocating that for a very long time, and i've gotten nowhere. down the line, far in the future, people will peruse these archives and wonder just why the heck it took you guys so long to realize that you should have been doing what i told you to do all along... -bowerbird
Hello Bowerbird (you DO know that that is an Australian Bird, don't you?) I have sent a collective reply to the group, which you have probably already seen. I apologize for my gaucherie in breaking into this specialist area, but I am starting to understand some of the issues. I writing the reply, I came to grips with what (forgive me if I'm wrong) is the primary issue: a canonical version of the text (even to the exent of honoring the line and page breaks in the original) that is embedded in a standardized XML framework. Converting lightly marked-up text to XML is one of the things that I do best. So if this is the direction that PGDP is taking, I might be of some use. Thanks for your time, John Redmond On Thu, 2009-12-17 at 21:07 -0500, bowerbird@aol.com wrote:
jim said:
Just to state the obvious, it sure would be cool if the work could be saved somewhere at that point in time when the work is still "reversible"
and, just to restate what has already been stated directly, you can save the work at almost any time in the workflow.
but what you will find is that the text isn't all that valuable at most points in the workflow, because it contains errors, not to mention that obtrusive and awkward "d.p. markup"...
even worse is that -- in order to justify their existence -- many proofers have taken to cluttering the text with "notes" that point out errors, instead of just fixing the darn things. (this means everything gets thrown on the postprocessor, so -- surprise, surprise -- postprocessing is now blocked up.)
the text is at its peak once the errors have been eliminated, right before the linebreaks and pagebreaks are discarded, so it would be great if it could be archived in _that_ state...
of course, it'd be even better if linebreaks and pagebreaks were to be actually carried over into the posted p.g. e-texts -- in such a way that they could be conveniently eliminated by anyone who wanted to do that, of course -- but i've been advocating that for a very long time, and i've gotten nowhere.
down the line, far in the future, people will peruse these archives and wonder just why the heck it took you guys so long to realize that you should have been doing what i told you to do all along...
-bowerbird _______________________________________________ gutvol-d mailing list gutvol-d@lists.pglaf.org http://lists.pglaf.org/mailman/listinfo/gutvol-d
participants (2)
-
bowerbird＠aol.com -
John Redmond