i think it would be marvelous to view the .pgtei file directly. why go through the pain of conversion if you don't have to? and the .pgtei file is the one with all the information in it, not? might as well view that, rather than some pale conversion... but let's get real here for a minute, ok? if the only people who can view the .pgtei file directly are the few who happen to be using a specific browser, there's no need to put a lot of resources in that direction. however, that's not really what lee is talking about, is it? no, it isn't. no sir. what lee is _really_ talking about is "openreader", which he has begun programming. (you _have_ begun, haven't you, lee? because there's no time like the present.) because, you see, a specialized e-book viewer-program (like openreader) can deliver an e-book experience that _far_surpasses_ the one that an end-user gets in a browser. and _that_ is the reason why people would want to view a .pgtei file directly, rather than look at an .html conversion; not because of the files per se -- it's silly to think end-users care anything about formats -- but because of the _viewer_ and the e-book _experience_ that was delivered therein... (savvy lurkers will recognize this as a straightforward variant of the argument i have been making all along...) so, if lee can deliver an openreader that is _cross-platform_ and runs on _older_hardware_, using _minimal_resources_, and can render the .pgtei file directly, giving the end-user a powerful e-book experience, all from a free-beer program, no one will use their funky web-browser to read an e-text... so let's wish lee success in his endeavor, for the ultimate good of all the end-users... -bowerbird p.s. when i try to view 16523-x.xml directly in firefox, it says: "this xml file does not appear to have any style information associated with it. the document tree is shown below." and then it shows me the document tree. how can i fix this problem?