Here is what I would propose as next steps, for each of the USX bible here:
Create a "resilient master document" (.silm file), say kjb.silm for the KJB...
It contains a small preamble, which can simply be copied from my lsg.silm, just changing the language: fr key to language: en when appropriate (and optionally the tile entry, so this is not critical for now)
And it must then list all the USX files orderly
Copy the style file lsg-styles.yml (or possibly use a symbolic link) to a style file with the appropriate name, say kjb-styles.silm
Run SILE+resilient as for the LSG.
Check and report errors or problems -- We could collect them below.
For instance, I just quickly did it for the KJB and noticed:
It errors on some input <char style="ft" closed="false">LORD</char><unmatched marker="+nd*" />
I haven't found this <unmatched> element in the USX 3.0 specs but I guess we could ignore it...
It uses <fr>/<ft> in notes, we'd need to skip the <fr> since we supplement it automatically -- for the record, the LSG used <xo>/<xt> notes. I probably didn't implement all of the sub-elements of the <note> element...
Some weird 3-letter words appear at the end or beginning of chapter: they turned out to be <toc3> elements, which I didn't filter out.
(Probably other things, I just had a glance...)
This would help ensuring the USX support is at least sufficiently complete for all the Bibles you gathered here.
What do you think of this?
Is this something you could do?
Hello Rob,
Now that you are bootstrapped with a running SILE+resilient setup and the LSG example at https://github.com/Omikhleia/awesome-sile-books
Here is what I would propose as next steps, for each of the USX bible here:
.silmfile), saykjb.silmfor the KJB...lsg.silm, just changing thelanguage: frkey tolanguage: enwhen appropriate (and optionally thetileentry, so this is not critical for now)lsg-styles.yml(or possibly use a symbolic link) to a style file with the appropriate name, saykjb-styles.silmFor instance, I just quickly did it for the KJB and noticed:
<char style="ft" closed="false">LORD</char><unmatched marker="+nd*" /><unmatched>element in the USX 3.0 specs but I guess we could ignore it...<fr>/<ft>in notes, we'd need to skip the<fr>since we supplement it automatically -- for the record, the LSG used<xo>/<xt>notes. I probably didn't implement all of the sub-elements of the<note>element...<toc3>elements, which I didn't filter out.This would help ensuring the USX support is at least sufficiently complete for all the Bibles you gathered here.
What do you think of this? Is this something you could do?