Open Omikhleia opened 10 months ago
With provided settings, these compiled without crashing (but of course the results have to be checked):
Failing:
ULT. It was still running so I stopped after some 3900 pages (41 MB) and it appears it contains sequences that are not encoded in USX but as raw text. That's a problem in the source USX file.
<para style="zaln-s" status="unknown">|x-strong="b:H7225" x-lemma="רֵאשִׁית" x-morph="He,R:Ncfsa" x-occurrence="1" x-occurrences="1" x-content="בְּרֵאשִׁ֖ית"<unmatched marker="*" /><char style="w" x-occurrence="1" x-occurrences="1">In</char> <char style="w" x-occurrence="1" x-occurrences="3">the</char> <char style="w" x-occurrence="1" x-occurrences="1">beginning</char></para>
Some conversion artifacts?
Added French bibles...
NCL = fails around p. 72 - we have to investigate it.
error summary:
Processing at: SILE/NCL/../../USX_test_versions/French/NCL/002EXO.usx:0:0: in \range-reference
Using code at: ...share/lua/5.4/sile/packages/resilient/bible/usx/init.lua:194: attempt to concatenate a nil value (field 'book')
FOB (~ 1410 pages, PDF 14.6 MB)
More French:
EDIT: I am tempted to say that punctuation encoding in the source is quite lame, though.
Greek
<para style="usfm">3.0</para>
which would have to be ignore rather than rendered.
- NCL = fails around p. 72 - we have to investigate it.
There are two books in NCS with empty headers <para style="h" />
: EXO and JAS.
While we could make the code not to crash, how are we going to guess the running header?
While we could make the code not to crash, how are we going to guess the running header?
This whole USX, USFM, USFX etc. is unsane. If supporting poorly designed XML schema (and I weight my words here) is a necessity for SILE 1.0, we are going to wait long. And I thought TEI XML was complex -- it's a pleasure compared to this...
NCL, with a hack for missing headers = 1770 pages without any other crash.
As part of this PR, I am also adding the TGCNT (Text-Critical Greek New Testament):
The latter point is interesting, as the current USX support in re·sil·ient just collates the notes in the page margin, but this is not using "true" insertions, so the amount of notes here cannot fit and overflows:
There are interesting challenges here to address, and this "small" bible is a perfect use case (besides Greek being nice, heh).
Aside note: Of course, we could use a much smaller font size and try to make all notes fit, but that wouldn't be fair ;)
N.B. My "task" here is done -- I'll remove the "Draft" status on the PR when resilient.sile 2.2.1 is released with the fixes identified here. I'd expect this to occur by the end of 2023.
Minimum supported versions (as of now):
Merry Christmas!
Ping.
Just used those files for quick regression testing phase with SILE 0.15 and resilient.sile 2.5 = An occasion to enable new features that were unavailable in 2023... Hence, minimum supported versions (as of now):
On my way, Just noticed after visiting this repository (but probably I also got a mail which I missed among all the GitHub notifications, my bad):
I'm afraid I have to reject the offer. I believe we are all walking a narrow road when it comes to making choices that align with our priorities and values, and I must stay true to my current commitments. It seems I lack the faith required to take this leap right now—but I admire your conviction and wish you the best of luck...
It seems I lack the faith required to take this leap right now—but I admire your conviction and wish you the best of luck...
To paraphrase one of your own message: I might be wrong, but from my following of the issues and discussions, I got the feeling that the world of digital Bible editions in a constant state of flux concerning the right way to do things, from USFM to USFX, USX and now USJ... It sure doesn't help one keeping interest and staying invested.
Closes #2
Work in progress,to check how good is the USX support in the re·sil·ient collection, and what needs to be fixed there:EDIT: As part of this PR, I am also adding the TGCNT, see comment.
EDIT: Issues noted in comment below addressed resilient 2.2.1.