Difference between revisions of "Talk:OSIS Genbooks"
(→Example OSIS Genbook -) |
(→Example OSIS Genbook -) |
||
| Line 90: | Line 90: | ||
== Example OSIS Genbook - == | == Example OSIS Genbook - == | ||
| − | The example/tutorial was developed a little more, but is not yet complete. It was developed by adding a conf file and generating the zip file used by one installer (bishop app). The files and a short description are at this [https://sword-2.github.io/library/genbooks/ | + | The example/tutorial was developed a little more, but is not yet complete. It was developed by adding a conf file and generating the zip file used by one installer (bishop app). The files and a short description are at this [https://sword-2.github.io/library/genbooks/ link]. No table of contents was observed for this module after installation. |
Also, root element attribute links were not found in the xml file. 3 of the 4 links in the root element were not found by a web browser when copied from the subsection "Example OSIS Genbook". | Also, root element attribute links were not found in the xml file. 3 of the 4 links in the root element were not found by a web browser when copied from the subsection "Example OSIS Genbook". | ||
Revision as of 23:50, 2 March 2023
Internal structure of a Genbook module made using xml2gbs
xml2gbs 1.0 is the OSIS/ThML/TEI General Book module creation tool for the SWORD Project.
The XML multilevel div element structure is converted by xml2gbs to a module internal structure that seems to deviate from the strict specification for OSIS. For example, the output of mod2imp BaptistConfession1646 contains the following IMP format references:
$$$ $$$/Confession $$$/Confession/Introduction $$$/Confession/Section 1 $$$/Confession/Section 2 $$$/Confession/Section 3 $$$/Confession/Section 4 $$$/Confession/Section 5 $$$/Confession/Section 6 $$$/Confession/Section 7 $$$/Confession/Section 8 $$$/Confession/Section 9 $$$/Confession/Section 10 $$$/Confession/Section 11 $$$/Confession/Section 12 $$$/Confession/Section 13 $$$/Confession/Section 14 $$$/Confession/Section 15 $$$/Confession/Section 16 $$$/Confession/Section 17 $$$/Confession/Section 18 $$$/Confession/Section 19 $$$/Confession/Section 20 $$$/Confession/Section 21 $$$/Confession/Section 22 $$$/Confession/Section 23 $$$/Confession/Section 24 $$$/Confession/Section 25 $$$/Confession/Section 26 $$$/Confession/Section 27 $$$/Confession/Section 28 $$$/Confession/Section 29 $$$/Confession/Section 30 $$$/Confession/Section 31 $$$/Confession/Section 32 $$$/Confession/Section 33 $$$/Confession/Section 34 $$$/Confession/Section 35 $$$/Confession/Section 36 $$$/Confession/Section 37 $$$/Confession/Section 38 $$$/Confession/Section 39 $$$/Confession/Section 40 $$$/Confession/Section 41 $$$/Confession/Section 42 $$$/Confession/Section 43 $$$/Confession/Section 44 $$$/Confession/Section 45 $$$/Confession/Section 46 $$$/Confession/Section 47 $$$/Confession/Section 48 $$$/Confession/Section 49 $$$/Confession/Section 50 $$$/Confession/Section 51 $$$/Confession/Section 52 $$$/Confession/Conclusion $$$/Appendix $$$/Appendix/Appx_Introduction $$$/Appendix/Appx_Section 1 $$$/Appendix/Appx_Section 2 $$$/Appendix/Appx_Section 3 $$$/Appendix/Appx_Section 4 $$$/Appendix/Appx_Section 5 $$$/Appendix/Appx_Section 6 $$$/Appendix/Appx_Section 7 $$$/Appendix/Appx_Section 8 $$$/Appendix/Appx_Section 9 $$$/Appendix/Appx_Section 10 $$$/Appendix/Appx_Section 11 $$$/Appendix/Appx_Section 12 $$$/Appendix/Appx_Section 13 $$$/Appendix/Appx_Section 14 $$$/Appendix/Appx_Section 15 $$$/Appendix/Appx_Section 16 $$$/Appendix/Appx_Section 17 $$$/Appendix/Appx_Section 18 $$$/Appendix/Appx_Section 19 $$$/Appendix/Appx_Section 20 $$$/Appendix/Appx_Section 21 $$$/Appendix/Appx_Section 22
Observe that the level 1 div elements with type="majorSection" had osisID="Confession" and osisID="Appendix" in the source XML file. Likewise, the level 2 div elements with type="chapter" had osisID="Introduction" and osisID="Section 1", etc. The use of the / separator within the module structure is why this separator is required in each internal osisRef string in order to make it work as a link. David Haslam (talk) 08:49, 25 June 2020 (UTC)
Example OSIS Genbook -
The example/tutorial was developed a little more, but is not yet complete. It was developed by adding a conf file and generating the zip file used by one installer (bishop app). The files and a short description are at this link. No table of contents was observed for this module after installation.
Also, root element attribute links were not found in the xml file. 3 of the 4 links in the root element were not found by a web browser when copied from the subsection "Example OSIS Genbook".
A stack overflow post what is the use of xsi:schemaLocation? had a question about a similar root tag, but that tag started with <beans xmlns ...>. An answer at the end by Mojun Zhu said "If you go into any of those locations, then you will find what is defined in those schema." For the stack overflow post, a web page was observed when the links were entered into a browser. But for the Example OSIS Genbook, a "not found" result was observed for 3 of the 4 the links.--Gregs650 (talk) 22:13, 28 February 2023 (UTC)
noted bug description unknown
The subsection “Making a Genbook module” noted a Windows bug. As written, readers may not comprehend the bug or its impact. Was the bug already reported to the crosswire support page so someone can look it up, investigate, or fix it? If reported, which bug reporting method was used - email, bug tracker, snail mail; what was date / subject / title? All this is to support Windows users.
