All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Michael Ryzhikov via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org,  Michael Ryzhikov <samonon@gmail.com>
Subject: Re: [PATCH] docs: remove {litdd} usage
Date: Mon, 23 Feb 2026 10:20:19 -0800	[thread overview]
Message-ID: <xmqq5x7nnwyk.fsf@gitster.g> (raw)
In-Reply-To: <pull.2215.git.git.1771846234706.gitgitgadget@gmail.com> (Michael Ryzhikov via GitGitGadget's message of "Mon, 23 Feb 2026 11:30:34 +0000")

"Michael Ryzhikov via GitGitGadget" <gitgitgadget@gmail.com> writes:

> From: samonon <samonon@gmail.com>
>
> *** Problem.
> {litdd} is used as alias for -- (when not inside backticks) because --
> is a reserved text in asciidoc. There is some problems with this:
> - need to remember that in some cases -- should be replaced with {litdd}
> - unnecessary config options when exporting adoc to other formats
> - in HTML it looks like "&#x2d;&#x2d;" instead of "--" (it works, but
>    browser should correctly decode hex symbols in html link:
>    see htmldocs/git-sh-i18n.html)
>
> *** Solution
> For better readability just escape -- using \.
> This is default asciidoc mechanism that don't need any configuration.
> Tested with "make all doc" - links inside linkgit: work.

Hmph, I do not quite see the point of this churn.  We'd need to
remember to do \-- instead of doing {litdd}, either way.

I do not know what you want to say with "when exporting to other
formats", as we already are formatting these source files into HTML
and manual pages.


  reply	other threads:[~2026-02-23 18:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-23 11:30 [PATCH] docs: remove {litdd} usage Michael Ryzhikov via GitGitGadget
2026-02-23 18:20 ` Junio C Hamano [this message]
2026-02-24  6:15   ` Михаил Рыжиков

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqq5x7nnwyk.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=samonon@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.