-
Notifications
You must be signed in to change notification settings - Fork 34
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
USX to Validate - PrintSpecialVerseSummary #48
Comments
- In USX, <ref> tags can appear everywhere, even in verses or headlines. Cross references in most formats are only allowed as parts of footnotes. Therefore wrap cross reference in a footnote. If you prefer the old behaviour, you can pass `-Dparatext.allowrefsoutsidefootnotes=true`. - Eliminate whitespace at end of verses when exporting to non-Paratext format. This can happen when importing from USX and a paragraph contains multiple verses separated by spaces. - Move whitespace at the end of formatting outside the formatting. This can happen mostly for \fr tags from USX. See #48.
I found some validation errors when importing from USX 2 and fixed them (used your example module from #42). If there are more left, feel free to share them in this issue. You can skip all whitespace validation by passing |
I don’t know which change is causing the error. Here's what happens now:
|
Thank you for sharing the subset in #47. Was able to fix this issue and also that subset now validates perfectly. In general when sharing modules under NDA, BibleMultiConverter has a ScrambledDiffable option that replaces all letters and digits by constants, but
I have now changed the scrambling to scramble all Unicode letters and digits regardless of script, and created a ScrambledParatextDump module that can do the same before converting Paratext to verse-based. So in case you still have trouble, you can run
(IMPORTANT If you leave out the Try if the bug appears as well if you use
instead of
and if yes, you can share the created dump file without sharing any actual text (you can verify it should contain mostly X and x). |
Yes, the bug appears. dump.zip |
When a validation error occurs, print a summary which other verses also contain validation errors. Also, when additional output (like special verse summary) is requested, try to print this even when validation fails. Validation errors are grouped into categories, and it is possible to ignore each of them separately (like you can ignore whitespace issues). See #48.
I am converting USX to Validate, and I use
PrintSpecialVerseSummary
argument.When I run the converter, I get the following warnings:
The text was updated successfully, but these errors were encountered: