YTang0648 wrote: What is this web interface really target to? what can we do to make this one differ from the rest of Bible site which is already there if cannot use those W3C standards? I really don't believe it is possible to serve blind people Bible without rewrite the UI. Will those text browser be able to play mp3 file of audio Bible? (I know sword do not have that, but it does not mean the sword cannot link to a site which have one)
And I reply: I you want to appeal to the lowest common denominator, then you cannot assume that browsers will support all of the specs properly. Yes, it would be great to be progressive and use all of the lastest standards. However, even the latest browsers and tools don't get the standards totally right. For example: As far as I know, no browser fully implements CSS2 (Opera may...) DreamWeaver, a very popular HTML editor amond professionals, spits out depreciated HTML4 tags and attributes. People still use old browsers like IE5, IE5.5, AOL ???, and Netscape 4.7. As far as frames go, I think they were the worst thing to happen to HTML. You can get far better results by creating "fake" frames with PHP. I have done this sucessfully for several of my clients. -- Matthew Donadio ([EMAIL PROTECTED]) _______________________________________________ sword-devel mailing list [EMAIL PROTECTED] http://www.crosswire.org/mailman/listinfo/sword-devel
