Re: [sword-devel] Versification/Encoding Issues
As for spelling, and as a fascinating learning experience, pick up your printed KJV Bible and examine the spelling of the word ankle[s] in Ezekiel 47:3 and Acts 3:7. Some editions have ancle, others have ankle. Ostensibly both streams are based on the Authorised Version of 1769. So Peter's advice is spot on. -- David Peter von Kaehne wrote: The consensus is that any module should be a faithful representation of the underlying printed text. The word spirt appears unfamiliar but is listed in dictionaries and presumably applicable in this situation. http://books.google.co.uk/books?id=z3kKIAAJpg=RA1-PA688lpg=RA1-PA688dq=to+spirtsource=webots=r2DFi9xSrfsig=-D3ScFVjY-OJZDhCqlVVyJ27jJchl=ensa=Xoi=book_resultresnum=4ct=result As the word exists and means what must have been meant I would take this as a useful learning experience that casual correction of texts is a dangerous undertaking. Yours in Him Peter -- View this message in context: http://www.nabble.com/Versification-Encoding-Issues-tp21341395p21349766.html Sent from the SWORD Dev mailing list archive at Nabble.com. ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
[sword-devel] Versification/Encoding Issues
I'm working on several bibles to get them into Sword Format (ultimately into public domain, or as close to PD as possible), and I've got a few unresolved issues. Can someone point me to the how-to that covers these topics? Issue number 1 - Versification standards One Bible I'm working on is The Jewish School Family Bible, Abraham Benisch, ~1852 http://www.archive.org/search.php?query=creator%3ABenisch%2C%20A This bible has Jewish versification. For example Hosea Chapter 1 has only 9 verses. JSFB Hos 2:1,2 are similar in content to the KJV Hos 1:10-11 . What to do about that? Change the versification? How do I make this sword compatible? Issue number 2 - Book Order For the text mentioned above, when I'm working on bibles with book order that doesn't match the KJV, Can I leave the order as they are in order to encode into VPL? into OSIS? That is, will sword front ends pick up a nonstandard order and reorder it for parallel display, or is it up to me? Issue number 3 - Missing Verses If I get to a verse That simply isn't present in the translation I'm working on, do I need to leave an empty verse row in VPL? in OSIS? Issue number 4 - Spelling mistakes in the text In a circa 1950 U.S. English Bible (*), I came accross spelling that is just wrong for English : spirts blood instead of spurts blood in the original text and in the OCR copy, is correcting such a spelling mistake encouraged or discouraged? In this case, the spelling S P I R T is used 3 times: twice in Lev 6:27 and in Isa 63:3--in place of sprinkle in the KJV, so it appears intentionally spelled that way. However, I don't see any theological reason for it, just the translator's quirky spelling. Is it OK to do minor spelling corrections like this when encoding? (*) This is from the Bible In Living English which I believe was published without copyright in the 1950's. However, copyright is claimed by the Jehovah's witnesses 25 years after the death of the Author. In the Watchtower copy I possess, the Author in in his own words writes about his work's free distribution in the preface (which implies public domain), which means the work had been released before he died. When you copyright a book that that is already in P.D., you MAY own the formatting and the page numbering, but not the text itself. It is my belief that similar to the Bible in Basic English, in the 1950's, if you didn't claim a copyright in writing when you originally published the work in the U.S., the work is public domain, and that can't be undone later. Steven's preface seems to confirm this, but I need to do more research into the history of the text and the law before any publication. Contacting the Watchtower is true to it's name. It's easy to get missionaries to come visit, but finding a legal department inside that tower is still eluding me. While the Watchtower published this book in 1972, up to his death in 1957 Steven Byington was NOT a Jehovah's Witness. He attended a United Methodist Church and had pretty harsh words about the New World Translation when it first came out. He apparently helped edit the NWT or had conversations with the Watchtower after the NWT was originally published that helped the translation correct some early errors. ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] Versification/Encoding Issues
Mike Hart wrote: I'm working on several bibles to get them into Sword Format (ultimately into public domain, or as close to PD as possible), and I've got a few unresolved issues. Can someone point me to the how-to that covers these topics? Issue number 1 - Versification standards One Bible I'm working on is The Jewish School Family Bible, Abraham Benisch, ~1852 http://www.archive.org/search.php?query=creator%3ABenisch%2C%20A This bible has Jewish versification. For example Hosea Chapter 1 has only 9 verses. JSFB Hos 2:1,2 are similar in content to the KJV Hos 1:10-11 . What to do about that? Change the versification? How do I make this sword compatible? Versification should be left as it is in the original. The import tools will adjust the verses so that they all fit into KJV versification for now, and when we have alternative versification support completed and released such Bibles will benefit from not having been altered. Issue number 2 - Book Order For the text mentioned above, when I'm working on bibles with book order that doesn't match the KJV, Can I leave the order as they are in order to encode into VPL? into OSIS? That is, will sword front ends pick up a nonstandard order and reorder it for parallel display, or is it up to me? Likewise, book order should be left as it is in the original. The current tools will ignore book order and every Bible will come out with KJV book ordering. The only problem would come if you used VPL without prepended verse refs, which you should really avoid. Issue number 3 - Missing Verses If I get to a verse That simply isn't present in the translation I'm working on, do I need to leave an empty verse row in VPL? in OSIS? Missing verses can simply be omitted. Issue number 4 - Spelling mistakes in the text In a circa 1950 U.S. English Bible (*), I came accross spelling that is just wrong for English : spirts blood instead of spurts blood in the original text and in the OCR copy, is correcting such a spelling mistake encouraged or discouraged? In this case, the spelling S P I R T is used 3 times: twice in Lev 6:27 and in Isa 63:3--in place of sprinkle in the KJV, so it appears intentionally spelled that way. However, I don't see any theological reason for it, just the translator's quirky spelling. Is it OK to do minor spelling corrections like this when encoding? If you find a genuine mistake, you should go ahead and correct that. But I would generally err on the side of assuming the author printer were correct. In this case, I don't think spirt is an error. It's listed in plenty of dictionaries. --Chris ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] Versification/Encoding Issues
Mike Hart wrote: I'm working on several bibles to get them into Sword Format (ultimately into public domain, or as close to PD as possible), and I've got a few unresolved issues. Can someone point me to the how-to that covers these topics? Please have a look at our wiki, which now is finally again up and running. We have extensive documentation on module making there. Issue number 1 - Versification standards One Bible I'm working on is The Jewish School Family Bible, Abraham Benisch, ~1852 http://www.archive.org/search.php?query=creator%3ABenisch%2C%20A This bible has Jewish versification. For example Hosea Chapter 1 has only 9 verses. JSFB Hos 2:1,2 are similar in content to the KJV Hos 1:10-11 . What to do about that? Change the versification? How do I make this sword compatible? Work is currently being done to enable diverging versification schemes. The idea is that a Bible will be encoded along its own scheme and not be pressed into KJV format. So my suggestion is that you encode the book in the way it was intended and hope that the work in the library and frontends etc will be done by the time you are ready to publish. Issue number 2 - Book Order For the text mentioned above, when I'm working on bibles with book order that doesn't match the KJV, Can I leave the order as they are in order to encode into VPL? into OSIS? That is, will sword front ends pick up a nonstandard order and reorder it for parallel display, or is it up to me? See above Issue number 3 - Missing Verses If I get to a verse That simply isn't present in the translation I'm working on, do I need to leave an empty verse row in VPL? in OSIS? See above Issue number 4 - Spelling mistakes in the text In a circa 1950 U.S. English Bible (*), I came accross spelling that is just wrong for English : spirts blood instead of spurts blood in the original text and in the OCR copy, is correcting such a spelling mistake encouraged or discouraged? In this case, the spelling S P I R T is used 3 times: twice in Lev 6:27 and in Isa 63:3--in place of sprinkle in the KJV, so it appears intentionally spelled that way. However, I don't see any theological reason for it, just the translator's quirky spelling. Is it OK to do minor spelling corrections like this when encoding? The consensus is that any module should be a faithful representation of the underlying printed text. The word spirt appears unfamiliar but is listed in dictionaries and presumably applicable in this situation. http://books.google.co.uk/books?id=z3kKIAAJpg=RA1-PA688lpg=RA1-PA688dq=to+spirtsource=webots=r2DFi9xSrfsig=-D3ScFVjY-OJZDhCqlVVyJ27jJchl=ensa=Xoi=book_resultresnum=4ct=result As the word exists and means what must have been meant I would take this as a useful learning experience that casual correction of texts is a dangerous undertaking. Yours in Him Peter ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
