the
standalone tar.gz? Seems the data is in texts/ztext/tr/nt.czz? I confess
I'm not a SWORD-wielder.
@DM: Will your corrections be using the exact same Greek text data as the
foundation?
Thanks.
--
Weston Ruter
http://weston.ruter.net/
@westonruter http://twitter.com/westonruter - Google
Profilehttp
On Sun, Jan 1, 2012 at 5:15 PM, Chris Little chris...@crosswire.org wrote:
On 1/1/2012 4:39 AM, DM Smith wrote:
On Jan 1, 2012, at 1:15 AM, Weston Ruter westonru...@gmail.com
in the Textus Receptus? Which digital edition of the TR are you keying
off of? Is it the TR
http://www.crosswire.org
? Are
there ongoing efforts to refine the data?
3) Is there a goal to refine the OT morphology to provide @src for the Old
Testament linkages to an available Masoretic Text, such as the Westminster
Leningrad Codex? I am interested in supporting this.
Happy new year!
--
Weston Ruter
http
.
To unsubscribe from this group, send email to
open-scriptures+unsubscr...@googlegroups.comopen-scriptures%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/open-scriptures?hl=en.
--
Weston Ruter
Founder
Open Scriptures http
___
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
--
Weston Ruter
http://weston.ruter.net/
@westonruter http://twitter.com/westonruter - Google
Profilehttp
to unsubscribe/change your settings at above page
--
Weston Ruter
http://weston.ruter.net/
@westonruter http://twitter.com/westonruter - Google
Profilehttp://www.google.com/profiles/WestonRuter#about
___
sword-devel mailing list: sword-devel@crosswire.org
need to break out our directory parsing code and make it work well with
a few of the more mainstream httpd services like Apache and IIS.
--
Weston Ruter
http://weston.ruter.net/
@westonruter http://twitter.com/westonruter - Google
Profilehttp://www.google.com/profiles/WestonRuter#about
at above page
___
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
--
Weston Ruter
http://weston.ruter.net/
@westonruter
prefixes on both sides of the dash?
Ap-Works
Apo-Works
Ap-Wo
How about abbreviations of just one side or the other:
Apo-Wrks
Apostle-Wrk
A-Wks
In Him,
DM
On 09/30/2010 01:24 PM, Weston Ruter wrote:
I think the fundamental problem here is that the SWORD reference parser is
too
to unsubscribe/change your settings at above page
--
Weston Ruter
http://weston.ruter.net/
@westonruter http://twitter.com/westonruter - Google
Profilehttp://www.google.com/profiles/WestonRuter#about
___
sword-devel mailing list: sword-devel@crosswire.org
settings at above page
--
Weston Ruter
http://weston.ruter.net/
@westonruter http://twitter.com/westonruter - Google
Profilehttp://www.google.com/profiles/WestonRuter#about
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org
.
Robert.
___
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
--
Weston Ruter
http://weston.ruter.net/
@westonruter http
gathering.
I got to meet some of you at BibleTech earlier this year, which was great. I
hope more of us can connect in person to get to know and support each other.
Weston
-- Forwarded message --
From: Weston Ruter westonru...@gmail.com
Date: Thu, Jun 24, 2010 at 8:59 AM
Subject
.
Weston
On Tue, Jun 8, 2010 at 12:37 AM, Weston Ruter westonru...@gmail.com wrote:
I've finished writing the OsisWork class for the Open Scriptures OSIS
module (osis.py): it can parse an existing OsisWork strings into its
component parts, allows these parts to be mutated, and then it can
Troy, This is great! Where's the source code for the reference parser?
As part of the Open Scriptures osis.py module for representing OSIS
identifier objects (osisID, osisRef, osisWork, etc), the next step is to
have a pluggable/extensible system for converting human-formatted references
into
end lately... because we had a baby two
weeks ago!
Weston
On Tue, May 11, 2010 at 9:32 AM, Weston Ruter westonru...@gmail.com wrote:
I'm working on a Python module for representing osisIDs (works, passages,
IDs, and refs). I think I've got the OsisWork class baked pretty well (at
least
Thanks for the news, Troy! This sounds to be very similar to the Bible
Knowledgebase that Sean Boisen has worked on at Logos. Is Steven's work an
open alternative? Is it a direct competitor?
Weston
On Sat, May 22, 2010 at 1:53 AM, Troy A. Griffitts scr...@crosswire.orgwrote:
Throughout the
into
a etc or splat list.
Thoughts? I'd love to get this implementation fully built out to be a
reference implementation for ports into PHP, JavaScript, etc.
Weston
On Tue, May 4, 2010 at 12:52 AM, Weston Ruter westonru...@gmail.com wrote:
Hello all,
Things have been a bit quiet on my end
Ledkovs
dmitrij.led...@ubuntu.com wrote:
On 11 May 2010 17:32, Weston Ruter westonru...@gmail.com wrote:
I'm working on a Python module for representing osisIDs (works, passages,
IDs, and refs). I think I've got the OsisWork class baked pretty well (at
least for reading/parsing), and I
/02/on-licensing-my-code/
Thanks!
Weston
On Tue, May 11, 2010 at 1:45 PM, Dmitrijs Ledkovs dmitrij.led...@ubuntu.com
wrote:
On 11 May 2010 19:58, Weston Ruter westonru...@gmail.com wrote:
Actually, it has to be open source because we don't have a paid GitHub
account :-) But you're right, I
Chris:
The version of the tagged OT text at http://github.com/openscriptures is
also in very good condition (prob better than the one at Crosswire). It
appears to only contain PD data - ie it doesn't include the more complete
morphology data which is copyrighted.
FYI, Strong's tagging is
Chris:
The version of the tagged OT text at http://github.com/openscriptures is
also in very good condition (prob better than the one at Crosswire). It
appears to only contain PD data - ie it doesn't include the more complete
morphology data which is copyrighted.
FYI, Strong's tagging is
Hello Kunio,
I love your idea. I forwarding your email onto the Open Scriptures group, as
there are many people there who I know would be very interested in your idea
and who share your desire for having open access to scriptural data. Your
described a need for a collaborative translation tool and
Thanks for the response, Karl. Responses appear inline below:
On Sat, Apr 3, 2010 at 5:34 PM, Karl Kleinpaste k...@kleinpaste.org wrote:
As a deeply network-centric person, I am always uncomfortable with any
specification that includes phrases such as use the closest server,
because the
the need for a single monolithic importer.
Thoughts?
Weston
On Mon, Apr 5, 2010 at 11:18 AM, DM Smith dmsm...@crosswire.org wrote:
On 04/05/2010 01:44 PM, Weston Ruter wrote:
DM:
But what we really need is not a parser but a tokenizer. I'm thinking about
writing one (my degree work
evaluate the quality of the submission.
In Him,
DM
On 04/05/2010 12:01 PM, Weston Ruter wrote:
Why not turn osis2mod into a web service? Then it wouldn't matter how it
is implemented since it would be abstracted away by the web service
interface. It could use the best XML libraries
FILENAME = sys.argv[1]
for chr_class, token in tokenize(open(FILENAME), CHR_CLASSES):
print .join(token).encode(utf-8), chr_class
James
On Apr 5, 2010, at 1:44 PM, Weston Ruter wrote:
DM:
But what we really need is not a parser but a tokenizer. I'm thinking
Last weekend at BibleTech:2010 I also presented a standardized URI space for
addressing accessing scripture.
Here's a draft with URI examples:
http://wiki.github.com/openscriptures/api/restful-uri-structure
Video of my talk: http://vimeo.com/10490211
Our idea is to implement this standard URI
Hi Robert,
Excellent question. Open Scriptures certainly doesn't need to be distinct
from CrossWire, and our values and principles are very much in line with
each other. But our focus is different, as you observed with Open Siddur.
CrossWire/SWORD is focused on developing (primarily) desktop and
If a feed isn't available, you could also simply use the HTTP Last-Modified
header (and/or Etag) to check if the source file has changed. This doesn't
help, though, if new editions are released as separate files, like
Tischendorf: http://files.morphgnt.org/tischendorf/
Weston
On Wed, Jan 13,
A year ago I did some initial work developing a PHP implementation for such
a parser:
http://open-scriptures.googlecode.com/svn/branches/php-prototypes/reference-parser.lib.php
Maybe the algorithms would be of use to you. I only refined it for New
Testament references.
On Fri, Nov 20, 2009 at
to
collaborate with you on it.
Thanks!
Weston Ruter
for the Open Scriptures project
___
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
...@gmx.net
Weston Ruter wrote:
Dear Crosswire,
Thank you for all you guys are doing to further open source Bible
software. I am writing inquiring about The Bible Tool. It appears to me
that development on it has slowed down, is that right?
Kind of. Troy and I have some definitive plans
-- Forwarded message --
From: Weston Ruter westonru...@gmail.com
Date: Mon, Feb 23, 2009 at 9:22 PM
Subject: Manuscript Comparator now with entire New Testament
To: Open Scriptures open-scriptu...@googlegroups.com
Huge progress has been made this week! The entire New Testament
34 matches
Mail list logo
