Hi Doitsu,
No, Sigil does not support epubcfi. IMO the epubcfi spec is yet another standard that seems to be overdone and not particularly useful especially in an epub that is being actively edited. It also depends strongly on how the dom deals with text, as a separate node or not. For example dom trees built by BS4 and gumbo differ in that regard. You can work around it but it is a pain since text nodes are not counted until the end.
In a final epub after all changes have been made, epubcfi can be useful to identify locations on the page that do not have an "id" attribute to indicate the destination. That said, node order strings including siblings and children accomplishes the same thing and is much easier to implement and understand.
As far as I can tell epubcfi's role in epub3.1 has been greatly reduced in comparison to epub 3 with its role in the opf using relative positions removed. It might be useful in a Reader, but is not particularly useful in an editor with constantly changing nodes.
Kevin
Quote:
Originally Posted by Doitsu
IMHO, it'd be better if the ACE checker would be a separate plugin.
Just running ACE checker and displaying the messages in a Web Browers would take only a couple of lines of code. However, since the ACE report doesn't use line and column numbers, it might be a bit tricky to reformat the output for use with Sigil. Also during my tests, ACE checker often crashed for no particular reason. Maybe we should wait until ACE checker is more stable.
Moreover, there doesn't seem to be much interest in accessibility tools....
@KevinH: It appears that ACE checker uses epubcfi to refer to locations in the epub. Does Sigil/Gumbo support epubcfi? |