Re: [sword-devel] PEG parser for USFM

Further to the thread late in 2015, in which I mentioned my User Defined Language file for Notepad++ I just put my USFM.xml file on GitHub. https://github.com/DavidHaslam/USFM I'm not promising to develop it further, but at least others can now access it. David -- View this message in

Re: [sword-devel] PEG parser for USFM

Dear Baiju, This github repo might be of interest. https://github.com/openenglishbible/USFM-Tools I've not delved any deeper. Blessings, David -- View this message in context: http://sword-dev.350566.n4.nabble.com/PEG-parser-for-USFM-tp4655560p4655855.html Sent from the SWORD Dev mailing

Re: [sword-devel] PEG parser for USFM

> Von: "Baiju M" > Two focusing specifically on converting to OSIS: > > https://github.com/adyeths/u2o > https://github.com/chrislit/usfm2osis > > Still you have used TextPipe to create the final OSIS file for Malayalam > bible! > > How is your experience with u2o.py,

Re: [sword-devel] PEG parser for USFM

On Wed, Jan 20, 2016 at 4:48 PM, Peter Von Kaehne wrote: > The problems are inherent in USFM - the lack of end marker, the lack of > semantics. > So you get all kinds of problems at chapter/chapter, verse/verse and > verse/chapter transitions. > And in poetry etc. Are you

Re: [sword-devel] PEG parser for USFM

Dear David, On Wed, Jan 20, 2016 at 2:39 PM, David Haslam wrote: > Dear Baiju, > > This github repo might be of interest. > > https://github.com/openenglishbible/USFM-Tools Thanks for the link. I will take a look at that project. Looks like we have few projects to

Re: [sword-devel] PEG parser for USFM

> Von: "Baiju M" > On Wed, Jan 20, 2016 at 4:48 PM, Peter Von Kaehne wrote: > > The problems are inherent in USFM - the lack of end marker, the lack of > > semantics. > > So you get all kinds of problems at chapter/chapter, verse/verse and > >

Re: [sword-devel] PEG parser for USFM

Baiju wrote, "Still you have used TextPipe to create the final OSIS file for Malayalam bible! How is your experience with u2o.py, did you got usable OSIS output? " I use TextPipe for lots of things, but in this context I used TextPipe only to analyse and fix some issues in the OSIS XML produced

Re: [sword-devel] PEG parser for USFM

On Mon, Dec 28, 2015 at 9:13 PM, Baiju M wrote: > Hi, > > 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 any

Re: [sword-devel] PEG parser for USFM

Sorry for top-posting, but this is FIO. More about PEG here http://en.wikipedia.org/wiki/Parsing_expression_grammar David -- View this message in context: http://sword-dev.350566.n4.nabble.com/PEG-parser-for-USFM-tp4655560p4655586.html Sent from the SWORD Dev mailing list archive at

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.

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

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

Re: [sword-devel] PEG parser for USFM

On 01/02/2016 10:48 AM, Ryan Hiebert wrote: 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

Re: [sword-devel] PEG parser for USFM

Ryan, Please visit http://paratext.org/about/usfm If you're a Windows user, you may find it helpful to download the CHM file http://paratext.org/system/files/usfmReference2_4.chm for handy reference when you have questions about USFM. Tip: If you have an iPad, your can read CHM files on the go

Re: [sword-devel] PEG parser for USFM

Another example, which may not be intuitive if you only read the USFM Reference. This is the correct way for Paratext to mark a Psalm title when it is [part of] verse 1. \c 5 \cl NKEMBILA YA 5 \d \v 1 Nkembila ya David. Yo me katuka na mukanda ya mfumu ya bayina ke yimbaka. Nkunga yai bo fwete

Re: [sword-devel] PEG parser for USFM

Not even sure how to submit it to Notepad++ let alone to Scintilla. I don't think it's yet good enough for submission. The main weakness is that markers within a line of text do not get highlighted unless there is a preceding space. Yet within the rules for USFM, there is no requirement for such

Re: [sword-devel] PEG parser for USFM

A word of caution. Although the USFM Reference 2.4 is the documented standard, the "de facto" standard is how Paratext works, and what it accepts. I've seen some strange things produced by Paratext users that one wouldn't imagine just by reading the Reference. Even so, when queried to one of my

Re: [sword-devel] PEG parser for USFM

> Von: "David Haslam" > btw. If anyone is interested, I made a decent attempt at creating a syntax > highlighting file for USFM to work with Notepad++. It's not perfect (I > doubt if perfection is achievable) but it is useful. Notepad++ uses the underlying Scintilla

[sword-devel] PEG parser for USFM

Hi, 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 any progress, will report here. Regards, Baiju M

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.

Re: [sword-devel] PEG parser for USFM

Hi Ryan, I would be happy to collaborate with you on this. I am also new to both USFM and PEG :) As you see in the repo, I am using Go programming language as the implementation language. I think we can make OSIS as the first targeted output format. On Dec 28, 2015 10:07 PM, "Ryan Hiebert"