Before you even begin to consider what the OSIS requirements are for updating the WLC module, you would need to gain a detailed understanding of the OSIS markup that was used by Osk in the module and to recognize the mistake that he made with regard to the spurious space that was included after every MAQAF, as well as to appreciate why this came about through his relying upon a script of his own that made no special provision for the morph segments that ended with a MAQAF.
My worry is that by jumping in with only the experience so far of tackling updates to works much simpler than the WLC in terms of markup, you could end up with an OSIS file that is even less satisfactory than was used for the last release.
The issues relating to Normalization of Biblical Hebrew are too complex to describe here in these comments. There is much more to be learned, my friend. See (e.g.) note 3 under
https://wiki.crosswire.org/Encoding#Normalization
The note refers to the more detailed coverage in
https://www.sbl-site.org/Fonts/SBLHebrewUserManual1.5x.pdf
There are lines in the file TanachHeader.xml that refer to "with exceptions set by the Donnelly/Kirk algorithm". The surname Kirk is that of Peter Kirk who in earlier years did some valuable research on how Unicode Hebrew vowel accents & cantillation points should be ordered for the text to display correctly when rendered by the smart fonts that were then available.
I have never been formally trained in the original Biblical languages, so I approached it with some trepidation when the opportunity was presented to get involved in a related but separate project in 2014. I came to the task as an engineer rather than as a linguist.
btw. It was I who persuaded Andrew West to provide the option in BabelPad for the custom normalization of Hebrew. He already had such an option for Tibetan.
Before you even begin to consider what the OSIS requirements are for updating the WLC module, you would need to gain a detailed understanding of the OSIS markup that was used by Osk in the module and to recognize the mistake that he made with regard to the spurious space that was included after every MAQAF, as well as to appreciate why this came about through his relying upon a script of his own that made no special provision for the morph segments that ended with a MAQAF.
My worry is that by jumping in with only the experience so far of tackling updates to works much simpler than the WLC in terms of markup, you could end up with an OSIS file that is even less satisfactory than was used for the last release.
The issues relating to Normalization of Biblical Hebrew are too complex to describe here in these comments. There is much more to be learned, my friend. See (e.g.) note 3 under
https://wiki.crosswire.org/Encoding#Normalization
The note refers to the more detailed coverage in
https://www.sbl-site.org/Fonts/SBLHebrewUserManual1.5x.pdf
There are lines in the file TanachHeader.xml that refer to "with exceptions set by the Donnelly/Kirk algorithm". The surname Kirk is that of Peter Kirk who in earlier years did some valuable research on how Unicode Hebrew vowel accents & cantillation points should be ordered for the text to display correctly when rendered by the smart fonts that were then available.
I have never been formally trained in the original Biblical languages, so I approached it with some trepidation when the opportunity was presented to get involved in a related but separate project in 2014. I came to the task as an engineer rather than as a linguist.
btw. It was I who persuaded Andrew West to provide the option in BabelPad for the custom normalization of Hebrew. He already had such an option for Tibetan.