Jan 2011
Keeping track
30/01/11 21:29
New working drafts of the OEB are continually being added to this site. In this stage of the OEB’s life, we aren’t widely promoting the OEB outside of this site, so here is the place to come to find what’s new.
The good news is that keeping track of the changes between working draft versions is easy. There are two main pages to keep an eye on.
The first is the list of closed issues on Github. This is a list of changes which have been recommended (why not recommend one yourself?) and implemented.
The second is the commit history - every change goes here, small or large.
This is not only a handy way to keep up to date, but also part of our commitment to you - to be open and transparent in all of our translation choices.
The good news is that keeping track of the changes between working draft versions is easy. There are two main pages to keep an eye on.
The first is the list of closed issues on Github. This is a list of changes which have been recommended (why not recommend one yourself?) and implemented.
The second is the commit history - every change goes here, small or large.
This is not only a handy way to keep up to date, but also part of our commitment to you - to be open and transparent in all of our translation choices.
How to help
18/01/11 10:32
It is always gratifying when people contact us and offer to help out with the OEB. Especially at this stage, proofreading is invaluable and we’d love all the help we can get - it is too easy to get lost in the text and overlook thing which are glaringly obvious to a new reader.
The question is always, though, how do I help?
To give this question a more structured answer, we’ve added a new page on the GitHub wiki. The How to Help page sets out briefly the current workflow for the OEB, and introduces Github’s Issues mechanism.
The wiki page explains that easiest way to help out is to download the current plain text version of the OEB (or read the Simple Html version), and look for typos, old fashioned language, inaccuracy, needed improvements etc. Then (with your GitHub account details) go to the OEB Issues Tracker, and add your suggested change!
This allows us to keep track of suggestions - and to show you our response. It is part of our commitment to an open, transparent editing process that gives readers confidence in the final product.
The question is always, though, how do I help?
To give this question a more structured answer, we’ve added a new page on the GitHub wiki. The How to Help page sets out briefly the current workflow for the OEB, and introduces Github’s Issues mechanism.
The wiki page explains that easiest way to help out is to download the current plain text version of the OEB (or read the Simple Html version), and look for typos, old fashioned language, inaccuracy, needed improvements etc. Then (with your GitHub account details) go to the OEB Issues Tracker, and add your suggested change!
This allows us to keep track of suggestions - and to show you our response. It is part of our commitment to an open, transparent editing process that gives readers confidence in the final product.
Rapid progress!
13/01/11 17:34
After a slow start to the project, we are now cooking with gas.
A full first pass of the New Testament has been made. This includes formatting, and updating capitalisation and hyphenation; but also includes removing the TCNT’s residual Elizabethan English and modernising the use of grammatical gender in line with current mainstream translations such as the REB and the newly revised NIV.
There are still no doubt typographical errors, and proofreading is required - I’d love any such mistakes pointed out to me so they can be fixed! Email me at my address at the bottom of the page.
The plan now is to have a period to fix clear errors and easily fixed clunkiness in the language, then to do an official release. Why not join the project and help out?
As usual you can read the current version of the NT from the links at the right.
A full first pass of the New Testament has been made. This includes formatting, and updating capitalisation and hyphenation; but also includes removing the TCNT’s residual Elizabethan English and modernising the use of grammatical gender in line with current mainstream translations such as the REB and the newly revised NIV.
There are still no doubt typographical errors, and proofreading is required - I’d love any such mistakes pointed out to me so they can be fixed! Email me at my address at the bottom of the page.
The plan now is to have a period to fix clear errors and easily fixed clunkiness in the language, then to do an official release. Why not join the project and help out?
As usual you can read the current version of the NT from the links at the right.
Welcome to 2011
03/01/11 19:51
Welcome to 2011! I hope you had a great Christmas.
Work on the OEB continues apace. The first pass of updating gender related language now covers all four Gospels, Acts and Romans with more to come.
As well, our GitHub account continues to be updated. We’ve split our rendering code into a separate repo called “USFM-Tools” with the aim that other projects will be able take advantage of it.
Check out the latest build from one of the links in the sidebar!
Work on the OEB continues apace. The first pass of updating gender related language now covers all four Gospels, Acts and Romans with more to come.
As well, our GitHub account continues to be updated. We’ve split our rendering code into a separate repo called “USFM-Tools” with the aim that other projects will be able take advantage of it.
Check out the latest build from one of the links in the sidebar!