>>>>> "RF" == Robin Fairbairns <[log in to unmask]> writes:
RF> david is right: to make assertions about the way the user
RF> interface "will be", you need to know whether your proposal is
RF> actually practicable. if any part of your proposal is not
RF> practicable, there's a danger that everything you suggest will be
RF> ignored, however good _some_ parts of it are.
To back this up with empirical data: I read until the two paragraphs
below "The Space Problem" -- and then immediately stopped reading.
These paragraphs made quite clear that the author didn't know a thing
about TeX constraints (and is erroneous about space handling in HTML
and XML as well). Obviously somebody who is new to technical details
of existing markup languages.
So the probability to find something worthwile in the rest of the text
was not high enough to spend the time reading further. If Robin
wouldn't have answered, I wouldn't have read any more of this thread
Martin, you might want to publish your document on tex-d-l,
de.comp.text.tex or comp.text.tex. There you will get better feedback
from potential users, and also from people who know TeX programming
since many years and who might explain to you which parts of your
proposals are reasonable and which aren't.
Joachim Schrod Email: [log in to unmask]
``How do we persuade new users that spreading fonts across the page
like peanut butter across hot toast is not necessarily the route to
typographic excellence?'' -- Peter Flynn