kovidgoyal said:
> A level of control where the user gets to specify font sizes of
> individual structural elements is simply out of place in a viewer.
> It would make sense in an editor, but certainly not a viewer.
i am of the position that the more power you give the end-user
to customize their reading experience, the more they love you. :+)
***
harry said:
> What is your viewer?
i've written a ton of 'em in the last two decades. the latest
is called "g.i.v.e." -- gutenberg intelligent viewer for e-text...
if anyone wants to see a beta of it, e-mail
bowerbird@aol.com
it's part of an overall package including "zen markup language"
-- also known as z.m.l. (slogan: "it's two steps past x.m.l.") --
which is now rapidly approaching a state of solid coherence...
the package grew out of research on the project gutenberg corpus
-- programmatic recognition of the structures inside the e-texts --
and i'm now working to make it robust across the entire tool-chain,
from authoring through web publication to cross-plat offline-viewers.
the essential philosophy is high-powered functionality via simplicity...
all of the pieces are there now, some more unpolished than others,
so if there's anything in particular you'd like to see, just let me know.
or hey, i guess i've even already announced some of it:
>
http://z-m-l.com/go/babelfish19.pl
>
http://z-m-l.com/go/vl3.pl
>
http://z-m-l.com/go/zmldingus093.pl
in terms of the specific interest here -- that is, _mobileread_ --
i'm of the opinion that the only mobile-readers that will survive
will be the iphone type -- i.e., internet-enabled, high-resolution,
with "reasonable" horsepower -- so that's all i'm worried about...
it's not that my apps couldn't run on a machine like the sony
-- my format and code is all relatively simple at its base --
but until that machine shows viability, i won't think about it...
-bowerbird