git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin von Gagern <Martin.vGagern@gmx.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Documentation: Strip texinfo anchors to avoid duplicates
Date: Wed, 03 Apr 2013 23:08:34 +0200	[thread overview]
Message-ID: <515C9A52.7020203@gmx.net> (raw)
In-Reply-To: <7vppyb4bu3.fsf@alter.siamese.dyndns.org>

[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]

On 03.04.2013 22:07, Junio C Hamano wrote:
> I see why duplicates are bad, but does that mean not having any is
> better?

I'd say yes: duplicate anchors cause current versions of texinfo to
reject the document outright, and older versions will likely cause a
broken interpretation of any anchor names.

What are possible scenarios where anchors could be useful?
a) Internal cross reference. I'm not sure whether texinfo checks for
   broken internal links. If it does, it did not report any.
b) Goto command issued by the user. I suppose most users would be happy
   with node-level navigation, and not use it for navigation to
   sub-node sections.
c) URLs in bookmarks or mails. I suppose people are more likely to use
   the html documents built by asciidoc, instead of a version
   constructed from the texinfo document. So not our issue.
Did I miss a relevant use case?

Automatically (or even manually?) generated unique names might be better
than none. But I'm not sure they are worth the trouble.

Martin von Gagern


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

      reply	other threads:[~2013-04-03 21:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-03 19:54 [PATCH] Documentation: Strip texinfo anchors to avoid duplicates Martin von Gagern
2013-04-03 20:07 ` Junio C Hamano
2013-04-03 21:08   ` Martin von Gagern [this message]

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=515C9A52.7020203@gmx.net \
    --to=martin.vgagern@gmx.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).