Moved the list of links on the right up a bit as a result.

Switched the ASCII hyphens to em dashes in the list of Fossil attributes belo. ... (check-in: 452726d6 user: wyoung tags: trunk)

• "indent" for cases where the only purpose was to indent things
• "blockquote" where you want an actual block quote in a wiki doc and thus can't use a "blockquote" element due to the historical misuse of this tag, preventing us from doing the same for it as we do for MD
• "sidebar" when the reason you wanted an indented paragraph was to create a sidebar; this is styled much like a blockquote in MD (or the new "blockquote" class in wiki docs) but floats to the right.

Using all three of these in the remaining www/ docs that still used explicit "blockquote" tags.

(If you're wondering why the prior commit claims to have dealt with all of these tags when this commit belies that, it's because this work was done en masse, then split up into two related commits to keep the commit messages more on-point. It was easier to commit these two chunks of work in this order. It would have required a complicated dance with the stash to commit them in the more logical order.) ... (check-in: 56c7c2cb user: wyoung tags: inskinerator-modern-backport)

• Constructs like "<blockquote><pre>" are now simply "<pre>"
• Ditto "<blockquote><b>" for command examples, which then allowed me to get rid of explicit "br" elements; pre does that for us.
• Where it was used merely to get an indent for a code block, we're now using pre or verbatim instead, depending on whether we need embedded HTML and/or pre-wrap handling. (Not the same thing as the prior item.) In some places, this let us replace use of HTML-escaped code blocks in pre with verbatim equivalents, not needing the escaping, allownig the doc source to read more like the rendered HTML.
• Use of blockquotes to get hierarchical indenting is no longer necessary; the skin does that. A good example is indenting ol and ul lists under the parent paragraph; additional manual indenting is no longer necessary.

The only remaining instances of "blockquote" under www/ are necessary:

1. The copyright release doc is plain HTML, without the fossil-doc wrapper, giving it no access to the new skin improvements.
2. One MD doc wants a blockquote in the middle of a list, and the current parsing rules don't let us use ">" there.
3. The skinning ...

As discussed with Stephan in /chat. File objects in the renamed case possess a 'priorName' property in addition to the 'name' reported in all cases. ... (check-in: f8d6e8c1 user: mark tags: trunk)

See this forum post for a test case and the trick previously needed to get Fossil to report "UNLINK" as a file's change status. ... (check-in: 4cca9033 user: wyoung tags: trunk)

• in Markdown nested lists, where blank lines should render the list items as separate paragraphs just as at the list's top level; since it does not, if you want a line break, you either have to wrap the item in "p" tags or do the double-br hack.
• in Wiki where blank lines within a list give you a separate list in the HTML output; this is fine for bullet lists, but with numbered lists it causes the numbering to restart unless you do the same sort of manual HTML workaround as with the prior item
• in plain HTML docs and wiki docs between "nowiki" tags

In many places, this cleanup gets rid of pointless stray "p" tags, placating HTML verifiers. ... (check-in: 1fd407f6 user: wyoung tags: trunk)

This removes the justification for the custom BusyBox configuration, which then means we can use Alpine's busybox-static package in the second stage, saving a bunch of network I/O and build time.

That in turn means we no longer have any justification for jailing the Fossil binary, since there's nothing extra left inside the container for it to play with. Doing this required bumping the Dockerfile syntax back up from 1.0 to 1.3 to get the "COPY --chmod" feature; tested it in Podman, which has had it for two years now.

Doing all of this simplifies the Dockerfile and its documentation considerably. As a bonus, it builds quicker, and it's nearly a meg lighter in compressed image form. Especially for the case of using the container as a static "fossil" binary builder, this is nothing but win. ... (check-in: 79ac06a5 user: wyoung tags: trunk)