Documentation: render special characters correctly
PATCH 1/1 Documentation: render special characters correctly
Three hyphens are rendered verbatim, so "--" has to be used to produce a dash. There is no double arrow ("<->" is rendered as "<→"), so a left and right arrow "<-->" have to be combined for that.
So fix asciidoc output for special characters. This is similar to fixes in commit de82095a95 (doc hash-function-transition: fix asciidoc output, 2021-02-05).
--- Documentation/git-fetch.txt | 2 +- Documentation/gittutorial.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
Documentation/git-fetch.txt +1 -1
@@ -133,7 +133,7 @@ remember to run that, set `fetch.prune` globally, or linkgit:git-config[1]. Here's where things get tricky and more specific. The pruning feature -doesn't actually care about branches, instead it'll prune local <-> +doesn't actually care about branches, instead it'll prune local <--> remote-references as a function of the refspec of the remote (see `<refspec>` and <<CRTB,CONFIGURED REMOTE-TRACKING BRANCHES>> above).
Documentation/gittutorial.txt +1 -1
@@ -322,7 +322,7 @@ initiating this "pull". If Bob's work conflicts with what Alice did since their histories forked, Alice will use her working tree and the index to resolve conflicts, and existing local changes will interfere with the conflict resolution process (Git will still perform the fetch but will -refuse to merge --- Alice will have to get rid of her local changes in +refuse to merge -- Alice will have to get rid of her local changes in some way and pull again when this happens). Alice can peek at what Bob did without merging first, using the "fetch"
Signature · 1 line
2.32.0
Quoted 7 lines · Andrei Rybak
Three hyphens are rendered verbatim, so "--" has to be used to produce a dash. There is no double arrow ("<->" is rendered as "<→"), so a left and right arrow "<-->" have to be combined for that.
So fix asciidoc output for special characters. This is similar to fixes in commit
de82095a95(doc hash-function-transition: fix asciidoc output, 2021-02-05).
Thanks. I looked at the doc-diff output before and after this patch, and they both seem like strict improvements.
The double-arrow thing is kind of weird to me in the first place, though. I suspect it might be more clear if it just spelled out what it is trying to say with words. Something like:
The pruning feature doesn't actually care about branches. Instead, it will prune local refs tracking remote ones as a function of...
But I'm OK to leave that to do on top; the current code simply renders incorrectly, and your patch is fixing that.
-Peff