git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH][RESEND] Escape some tilde characters causing spurious subscripts in documentation

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 24, 2007, 10:07 UTC
Message-ID
<7vbqf5wtrb.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<31e9dd080706231722v760b5a0cnc31e24b83deafb90@mail.gmail.com>
"Jason Sewall" <jasonsewall@gmail.com> writes:
Show 12 quoted lines
> On 6/23/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
>
>> I just checked with my copy of asciidoc, though, and there is no mangling
>> going on, at least in git-bundle.html (which is the only file I checked).
>> My asciidoc is version 8.2.1. What is yours?
>
> I've got 8.1.0; perhaps that's the problem. I wasn't so surprised to
> hear the asciidoc 7 and 8 don't get along, but I'm surprised to see
> that 8.1 and 8.2 are so different.
>
> Anyway, 8.1.0 is apparently what's in Fedora 7 (the distro I'm using
> right now) so it might be worth hanging on to the patch.

FWIW, 7.1.2, 8.2.1 and 7.0.2 all seem to be Ok (the last one is used to format the pages in html and man branches of git.git). It is a bit annoying having to use name\~num at some places and no backslash all others.

Two requests:
 - Documentation/git-rev-parse.txt has '{tilde}<n>'.  If you
   replace that {tilde} with a "~", how does your AsciiDoc
   format it?  Do you see the same breakage?
 - If it breaks, does it fix the breakage if you prefix the "~"
   with a backslash, instead of using {tilde}?

If the answer to both questions are "yes", then perhaps we should get rid of the {tilde} macro we define in Documentation/asciidoc.conf file, and use your "\~" solution everywhere.

Also do you see any pattern? It does not seem that all the "master~3" are broken for you but only some. If your commit message can describe when quoting is needed, that would help people who would modify the documentation in the future.

Previous: Johannes SchindelinNext: Jason Sewall
Message 5 of 10 in “[RESEND] Escape some tilde characters causing spurious subscripts in documentation”
  1. [RESEND] Escape some tilde characters causing spurious subscripts in documentationJason Sewall, Jun 23, 2007
  2. Johannes SchindelinJun 24, 2007
  3. Jason SewallJun 24, 2007
  4. Johannes SchindelinJun 24, 2007
  5. Junio C HamanoJun 24, 2007
  6. Jason SewallJun 24, 2007
  7. Jason SewallJun 24, 2007
  8. Junio C HamanoJun 24, 2007
  9. Jason SewallJun 24, 2007
  10. Junio C HamanoJun 24, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.