people who are building the programs that will use the pagescans need to be the ones that specify the conventions in making them, in consultation with the people who are actually doing the scanning. marcello, i don't see that you have much expertise on either end... that's not to say that your set of recommendations is all that bad. it's not that much different from the set i laid out some time back. (although in the places that it is different, mine is the better plan, reflecting experience in scanning and developing scan-using apps.) in direct response to david, just keep scanning the way you want, the way that works best for you. we can deal with what you create after the fact, if necessary. we'll have some feedback on workflow that we think will be mutually beneficial, but whatever you do, know for now that we can deal with your output, so just keep on scanning. -bowerbird p.s. as i feared, the current examples of pagescans in the library are case-studies in how _not_ to do it, for reasons i will list later...