At one point I had the goal of making Bike’s HTML representation look exactly like the in app representation. The main driver was so that I could use web view to show Bike file previews in macOS finder. After some trial and error I ended up using a more native solution for macOS Finder previews, so the work on Bike to HTML has fallen by the wayside…
But if you are interested in Bike > HTML @Blake Did some nice work in that direction here:
I’m not sure what to do about that. My goal is to say that Bike writes XML using a subset of HTML tags:
<?xml version="1.0" encoding="UTF-8"?>
<html xmlns="http://www.w3.org/1999/xhtml">
When I put a Bike document into a pure XML validator it seems to validate well. Other validators start to interrupt the document as some HTML variant and then it doesn’t validate.
If there’s some way I can change the header construction to make it “right” I’m happy to do that, but I generally want to write as XML without too many other promises, other then that I’ll be using a subset of HTML tags.
I can see how this would be useful, but I can also see how the current behavior could be useful, and the current behavior is more consistent with how pasting in general works. I think for now I would prefer that you just handle this as you are, with a post processing script.