>I grabbed the Project Gutenberg version of KJV Bible, and BOM (did you know they had that?)
just an fyi, it's the 1830 version - different chapters and no verses, a few typos, a handful of textual changes and a whole lot of extra "and it came to pass" ;-) Josh Coates www.jcoates.org -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of jb Sent: Monday, April 25, 2005 9:04 AM To: BYU Unix Users Group Subject: Re: [uug] Scriptures Gary Thornock wrote: >>like instant access. What READER do you recommend (both for >>RedHat 9 and FC2) and then which version (PDF, HTML, Plain Text) >>of the scriptures/manuals to download >> >>I've been using a plain HTML version of the Scriptures for the last >>few years. The one I have doesn't have the chapter headings, the >>topical guide, the footnotes, etc., but it does have the full text, >>and for the most part that's all I need. >> >> >> I'd have to agree, but with the addition that, if you use HTML, you get a lot more ability to organize/program the stuff the way *you* want it. [Storytime] When I was on studying medieval manuscripts in Paris I wrote a simple PHP/MySQL site to collate different versions of stories, poems, etc. It was a simple hierarchal tree with each branch ending in a content node. One of the great aspects of using an HTML display with PHP/MySQL in the background was that I could run it locally on my Zaurus palmtop. One Sunday I realized I could use the same system for the scriptures. I started with a root node of "scriptures", a node for each physical book (Bible, Triple). Eventually, I made it down through books (Genesis, 1 Nephi), to chapters and verses. The whole thing was a single PHP page, with a single GET parameter: The database ID of the current object. I grabbed the Project Gutenberg version of KJV Bible, and BOM (did you know they had that?), did some regex, left the headers in as objects, and voila! I had a very easy to manage PDA version of the scriptures. (I never got around to grabbing the Doctrine and Covenants.) I still use it from time to time. [/Storytime] So, in short, I agree that going with HTML, or a similar text-based markup language, is definitely the way to go. --jeremy -------------------- BYU Unix Users Group http://uug.byu.edu/ The opinions expressed in this message are the responsibility of their author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list -------------------- BYU Unix Users Group http://uug.byu.edu/ The opinions expressed in this message are the responsibility of their author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
