Re: [sword-devel] Announcing Sword++

e happy enough with the original library, it's quite unlikely that we'll see a mass exodus to a misguided fork. Inertia has the advantage. I hope this comes across as a reasonable, balanced perspective on the competition of forks, even in a small community. Yours in Christ, Ryan Hieb

Re: [sword-devel] PEG parser for USFM

> On Jan 2, 2016, at 7:21 PM, Kahunapule Michael Johnson > wrote: > > Also, one word of caution: There is no proper way to do a one-to-one, > lossless, round tripable correspondence between USFM to OSIS. Thank you for your help, I'm finding your emails most helpful. Because I'm doing this wi

Re: [sword-devel] PEG parser for USFM

> On Jan 2, 2016, at 2:54 PM, David Haslam wrote: > > Please visit http://paratext.org/about/usfm > [snip] David, thanks for your assistance. Indeed, I've already become fairly familiar with the 2.4 USFM spec, and my attempts to implement that specification in a PEG grammar are what prompted

Re: [sword-devel] PEG parser for USFM

I'm completely new to USFM, so I'm sketching out my ideas on how the parser probably should look. This is unearthing some of the many things I don't understand about USFM, so I'll post my questions here. Feel free to forward me to a better forum if there is one. These questions are all related:

Re: [sword-devel] PEG parser for USFM

> On Dec 28, 2015, at 9:43 AM, Baiju M wrote: > Anyone tried to create a parser for USFM using Parsing Expression Grammar > (PEG)? > > I just started exploring this idea here: https://github.com/baijum/usfm > This is very early stage. If I am able to > make an

Re: [sword-devel] usfm to osis converter...

This seems like very good work, Ryan. I took a look at the coverter before, as I'm a Python dev, and couldn't hack it. I tried to start wrting a OSFM parser, but I had some difficulty fully understanding what the spec was saying. Anyway, if you were interested in continuing to work on it, I'd be

Re: [sword-devel] New Front End

> On May 13, 2015, at 3:26 AM, Matěj Cepl wrote: > > On 2015-05-12, 19:34 GMT, Ryan Hiebert wrote: >> If I were you, I'd host the code and the tarballs on GitHub. >> Not everybody agrees with me, but GitHub is pretty capable for >> this purpose. >

Re: [sword-devel] New Front End

If I were you, I'd host the code and the tarballs on GitHub. Not everybody agrees with me, but GitHub is pretty capable for this purpose. > On May 12, 2015, at 2:30 PM, David Judah's Shadow Blue > wrote: > > I am about to make my first release of BIBISH, my new console front-end for > sword,

Re: [sword-devel] A call for Python programmers ...

I am a full-time Python developer, but I’m not very familiar with USFM or OSIS, so that’s where I’m lacking knowledge. I’ll read over the code on Github (I’ve already started), but I’m wondering if anyone has any pointers as far as good references for learning about those two formats. Ryan

Re: [sword-devel] DVCS (was Re: Project "Free Scriptures" started)

On Sun, Mar 16, 2014 at 4:14 PM, Matej Cepl wrote: > On Sat, Mar 15, 2014 at 07:25:15PM +0100, rj_qgsous_sword wrote: > >> and its Windows support (as of 2010) was reported to be much worse than >> Hg's. >> > > Let me emphasize "as of 2010" ... I don't use Windows myself (see the email > address)

Re: [sword-devel] DVCS (was Re: Project "Free Scriptures" started)

eally is amazing for that. I would personally consider the choice of whether to use GitHub (or another code collaboration site if you must) to be a strong indicator as to whether you want to have more people involved and helping. Ryan Hiebert a l

Re: [sword-devel] sword.js

Sounds like it would be better to look at the mods.d folder inside the main zipped package. — Sent from Mailbox for iPhone On Fri, Jul 12, 2013 at 9:44 AM, Greg Hellings wrote: > On Fri, Jul 12, 2013 at 11:37 AM, Stephan wrote: >> I want to provide an API to get a list of all modules in a repo

Re: [sword-devel] sword.js

ently? On Mon, Jul 8, 2013 at 2:06 PM, Greg Hellings wrote: > > > > On Mon, Jul 8, 2013 at 3:56 PM, Ryan Hiebert wrote: >> >> Have you looked at untar.js? >> >> >> https://code.google.com/p/bitjs/source/browse/untar.js?r=0eca1f06d91e1477e3708531939c8071fc87

Re: [sword-devel] sword.js

Have you looked at untar.js? https://code.google.com/p/bitjs/source/browse/untar.js?r=0eca1f06d91e1477e3708531939c8071fc877855 On a tangentially-related note, I've done some work on a python sword zmodule reader. It's stalled a bit now, because I've seen recommendations to use the C++ libraries,