Fossil

Several new keywords have been added over the past six years, this commit may accidentally include settings that aren't actually accepted by the server any more. Fix if you see them. ... (check-in: d25826d4 user: brickviking tags: bv-corrections01)

Grammar mistakes are even rarer. ... (check-in: 3fcd5bd4 user: brickviking tags: bv-corrections01)

Follow-up: Too many incompatible systems discovered. And too much push-back. The revolution is over. So sad....

Put the new section before "There Is No Staging Area" as that follows on from these ideas, then calved off the subsequent section "Commit Splitting" because it covers related but separate ideas. Together, these three form a conceptual whole that is considerably clearer than the prior presentation. ... (check-in: 5f5452f1 user: wyoung tags: trunk)

This occurs in all timeline modes, including the classic, compact, and verbose views. The result is that the corners for these selected row types are rounded, but because they tend to be compact, it gives a full-round look on the ends. Avoiding this would require considerably more verbose CSS, and it's plenty intricate as it is. ... (check-in: 9568091a user: wyoung tags: trunk)

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)

At the moment, it is a straight copy with the intent of forming a baseline for the minimal changes I'm about to make in order to allow the Fossil doc changes on this branch to render reasonably. ... (check-in: 7d8631f1 user: wyoung tags: inskinerator-modern-backport)

• "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 ...

Credit for this goes to Stephan Beal (the eminent repo archaeologist) plus whichever "anonymous" posted this ticket, way back in 2010! ... (check-in: 6f94da9b user: wyoung tags: inskinerator-modern-backport)

Inskinerator Modern uses that rule to shift all the ancillary colors when you shift one of the primaries, saving the user from having to specify each derived color name manually. Fossil's hard-coded skins don't have that same motivation, and as hard-coded defaults, the old "office highlighter" colors were fine, but once you get down to specific instances, we don't want to use arbitrary color, we want them to be analogous or complementary to the main accent color. ... (check-in: 285defac user: wyoung tags: inskinerator-modern-backport)