Technical issues and status of the project

The posts for the rest of the psalms are completed and scheduled. I wish I could make these posts easier to study and read.

I did demonstrate with the very short Obadiah that I could separate the music for every verse and use the SVG file type (in an embedded html file). This works in the e-pub software without difficulty, so I could use the technique and in principle code the html automatically. It's possible that with a custom short page length, I could make SVG images that have a suitable length and border so that they need no further manual processing. I used a manual process for the 21 images for Obadiah. 2,527 images for the whole book of psalms would be, however, too many to handle. I wonder if 4 verses at a time would make the process work so that the text and the verses could be integrated on a single 'page'. But how big is an e-page? Indeterminate.

Unfortunately blogger does not support SVG images or integrated music software. So for the current presentation of the raw material of the psalms, and the other bits and pieces I have included on the blog in the past few months, to read the text and the music together, I suggest bringing up the post in two different windows and reading one beside the other phrase by phrase.

In the meanwhile, when Psalms and the first chapters of Job are complete -- next week -- I will slow down if not stop this series. 

I hope to see if the e-pub will support the data more easily. I expect I can automate the content for a chapter including images and performance links. [I have automated the first chapters of Job for the e-pub format with svg images. A far better delivery mechanism than blogging. I have divided the chapters by four lines of music. This is better for poetry than prose but works for both.]

But I can't automate the correction of the WLC against mgketer. That has the advantage of slowing me down. Then I might see more of the scenery and learn whether the music will yield more secrets.