kavitharaju

To determine what the "type" is > You can't determine the type from syntax alone^1. I.e. you can't work it out with a parser. Instead we have defined an extension...

That is in our plan. Hopefully in a couple of months we would be able to get the early versions out. Here is an issue for you to keep watch...

Using USFM/X committee's test suite. Current status https://github.com/Bridgeconn/usfm-grammar/pull/182#issuecomment-1283951776

Current Status * Total USFM samples in the test suite = 249 * No. of positive tests = 197/249 * Correctly parsing(Generating syntax tree and/or errors) = 184/249 * The...

Another update https://github.com/usfm-bible/tcdocs/pull/44

Upon pulling latest tests from [tcdocs](https://github.com/usfm-bible/tcdocs/tree/0a66c546d773f8452a3a1baf5541511d3f9c87bf/tests), finding these grammar rule changes in test suite even though https://docs.usfm.bible/usfm-usx-docs/latest/index.html doesn't reflect most of them yet: 1. \fig is allowed in \f, as...

List of APIs and discussion on their names are [here](https://bridgeconn.sharepoint.com/:x:/r/sites/DevTeam-USFM-Grammer/Shared%20Documents/USFM%20-%20Grammer/API%20names%20discussion.xlsx?d=wd7e55341159e469eb2a2f1de62934180&csf=1&web=1&e=Mho28q)

We don't have support for peripheral parsing yet. [Disclaimer](https://github.com/Bridgeconn/usfm-grammar/blob/master/docs/Disclaimer.md)

Note: In python could use https://docs.python.org/3/library/profile.html to find out where improvement is needed

Thank you for your interest in the tool. Yes contributions are very welcome. By the time you are working on it let us know. We can create a feature branch...