Plugin Development

[KevinH]

Ignoring the AI aspect of all of this.

Although a plugin like this is doable, there really is not a lot of need for one.

Let me explain.

Normally, authors of books write and do primary editing of their books in a Word Processor like LibreOffice or Word remembering to properly specify and use styles.

Then the epub dev person can either export that word document as html to load it into Sigil or use one of the existing Sigil import plugins to load it. There is very little need to create lots of html by hand. Next Sigil has the ability to use user supplied text Clips. Many users assign a few of the most common html tags to the clip so they can insert them with a single click on any of the 40 clip icons Sigil supports.

Sigil already starts every page with the proper xhtml framework that is equivalent to what your example haml code would produce but for Sigil, since epubs need proper xhtml, Sigil uses that not the more loosely formatted xhtml.

So rarely do epub developers need to hand create large blocks of html/xhtml code. They in fact spend a large part of their time cleaning up the poor html most other programs create, adding the proper css styling, reformatting footnotes, adding images, cover, etc and even javascript if needed.

Now if you know of a good html editor that produces haml, then by all means you could create and use a plugin to read it in and convert it to xhtml.

Alternatively you could run a standalone program to convert haml to html and then import that to Sigil right now.

Hope this explains things better.