-
-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unclosed \fe breaks usfm parser #467
Comments
In what context is this occurring? When you try to translate a book? |
Yes:
Line numbers may not match perfectly, because I have some local changes (logging things). |
This issue is related to a host of issues with the USFM parser we are using in the translate script. We are in the process of replacing it with a parser that isn't as strict. |
@isaac091 Can we close this issue? |
I didn't close it initially because I couldn't test the exact book, but I would imagine it did get fixed with the change. |
I'm getting
missing caller parameter after \\{token.name}
because ofmissing caller parameter after \fe
. For example, a line of USFM:The text I'm working with actually has a bunch of these. I realize this is probably not valid usfm (I'm not sure), but is there a way to be less strict in parsing it and allowing the
\fe
to implicitly close?(Perhaps related to #201)
The text was updated successfully, but these errors were encountered: