The cursor is actually on the first <, not "before it.
so if CV shows something like |<tag> , then the cursor is in the tag. If you had a block cursor it would highlight the < but CV uses an insertion point cursor.
The long held Sigil rule is you can not split when in a tag. If you think this is too tight, the I would be happy to consider a patch or PR that handles just that one case.
Note, a file with an xml file extension can be of any type, it could be an opf, an ncx, an xhtml, a generic xml file, etc. There is no way to know the tag meanings: a body tag may not be what you think it means, there may be no html root tag, there is no way to tell which are void tags and which are not, which are block tags and which are not, where it might even be safe to split, and how splitting will impact a generic xml file.
And according to the epub3 spec, file extension must be xhtml if the file is an xhtml file.
The first step when seeing lots of xml files that are really xhtml files (or html files that are really xhtml files) is to use Sigil's ability to bulk rename a set of files by just changing the extension as they do not meet the current epub spec left as .xml files.
Again, I would consider a patch or PR to handle this differently but Sigil has long operated this way, and forcing people to change file extensions to more correct ones that meet the latest spec makes good sense to me. Please note, that old epub2 spec that allowed pure xml "islands" has long been deprecated mainly since no reader bothered to support it and just treated all .xml files as .xhtml files. This changed in epub3.
Hope this explains why you are seeing what you are seeing.
Quote:
Originally Posted by BeckyEbook
First case- Open any file, place the cursor in front of any open or close tag, and try to split the file (Split At Cursor).
Message: File cannot be split at this position.
Why?  After all, it is enough to move the cursor one field to the left and then the split will work.
Second case- Open any file, but change the extension from xhtml to xml (I see files like that in the wild quite often).
- Place the cursor anywhere (apart from the one I described in the first case of course) and try to split the file (Split At Cursor).
Message: Cannot split since it may not be an HTML file.
Despite the message, the split will be performed ... but the split part of the file will be lost (we lose a piece of code BEFORE split position, and it remains AFTER split) 
|